Bug 835349 – ls/rsync Value too large for defined data type

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description LABBE Corentin 2022-03-15 17:54:17 UTC]

Hello

I have a cubieboard2 under gentoo ARM which I use since a long time.
Usage is to mount a CIFS share and to rsync it.
It was not updated since years, only kernel was updated (5.15).

Until today it works fine, but I started to upgrade it via binary packages generated from a qemu running recent stage3.

Now doing ls or rsync on the share give:
Value too large for defined data type
But "busybox ls /mnt/" is still working.
So the problem is unrelated with the share and/or kernel.

Reproducible: Always

[Comment 1 Sam James 2022-03-15 18:03:51 UTC]

I think we need more details here:

1. emerge --info;
2. exactly which packages changed (use qlop or similar to get a full list, to identify before/after please)
3. anything else you can share that sounds relevant

[Comment 2 LABBE Corentin 2022-03-15 18:42:09 UTC]

I am sorry I clicked too soon open before I collect emerge --info.
But the board is now remotely dead since bash was upgraded but ncurses not AND watchdog was using a bash script.
So basicly I will cannot provide more information until a month (I need to go in its location).

But I am sure the problem started just after I upgraded to sys-libs/glibc-2.33-r13 (probably from 2.27-r6).

[Comment 3 Sam James 2022-03-15 18:44:49 UTC]

(In reply to LABBE Corentin from comment #2)
> I am sorry I clicked too soon open before I collect emerge --info.
> But the board is now remotely dead since bash was upgraded but ncurses not
> AND watchdog was using a bash script.

If you were upgrading in a screen session or tmux, it should carry on and upgrade as needed. Although it should be fine with preserve-libs in the intermediate part anyway...

> So basicly I will cannot provide more information until a month (I need to
> go in its location).
> 
> But I am sure the problem started just after I upgraded to
> sys-libs/glibc-2.33-r13 (probably from 2.27-r6).

I understand, and it likely is related, but need the full picture.

[Comment 4 Jonas Stein 2022-03-25 00:19:44 UTC]

It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

Before you reopen: We need to have all information at hand before ticket assignment. This includes
* the complete build.log as attachment and
* a paste of the emerge info 
as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/