Re: cp giving input/output error

[Paul Eggert]

"Campbell Smith, Peter" <address@hidden> writes:

>> From: Paul Eggert [mailto:address@hidden
>> What does 'strace -o trace.tr cp old new' say?
>
> It gives about 240kbyte of trace info, ending with the following:
> ...
> read(3, "\1\1\367\6LVAL\0\0\0\0\2\0\274\10\t\7\0\0\0\0\0\0\0\0\0"..., 4096) = 
> 4096
> write(4, "\1\1\367\6LVAL\0\0\0\0\2\0\274\10\t\7\0\0\0\0\0\0\0\0\0"..., 4096) 
> = 4096
> read(3, 0xbfffe740, 4096)               = -1 EIO (Input/output error)
> write(2, "cp: ", 4)                     = 4
> write(2, "reading `/smbfs/aravis/idtsales/"..., 76) = 76
> write(2, ": Input/output error", 20)    = 20

It looks like "cp" is doing the right thing, then: the operating system
is reporting an I/O error, and "cp" is passing that along to you.

There may be a bug in the operating system, or in the file system
code, or something like that; but that would most likely be outside of
coreutils's purview.