On 2026-09-08 11:06, Lenard Frommelt wrote:
It looks copy failed with the openat() here:
`openat(AT_FDCWD, "/path/to/some/archive/targetfile", O_WRONLY|O_CREAT|O_EXCL,
0600) = -1 EOVERFLOW (Value too large for defined data type)`
So it seems the openat() with create flags just fails right there, returning -1
which then is interpreted as a size.
No, -1 merely means openat failed. EOVERFLOW likely means that either the file
already exists and has an inode number or size that don't fit into your app, or
the file doesn't exist but if created would have an inode number out of range.
Is your mv a 32-bit executable? If so, I suggest building 64-bit coreutils as
that should be a simple workaround. Regardless, the problem is somewhere in
your file system or kernel; it's not in mv.
As this is not a coreutils bug I'm taking the liberty of closing the bug report.
