Rsync rsync: writefd_unbuffered failed to write ?
Matt McCutchen
matt at mattmccutchen.net
Thu Dec 13 15:20:12 GMT 2007
On Thu, 2007-12-13 at 09:48 -0500, Scott Parry wrote:
> I have enclosed the log for you to take a look at.
> I am running this from the root account.
Ah, this part beginning on line 30371 seems to be the root of the
problem:
22250 write(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144 <unfinished ...>
22248 <... read resumed> "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) = 262144
22250 <... write resumed> ) = -1 EIO (Input/output error)
22248 select(5, NULL, [4], [4], {60, 0}) = 1 (out [4], left {60, 0})
22248 write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6400 <unfinished ...>
22250 write(4, "S\0\0\10rsync: write failed on \"/mnt"..., 87 <unfinished ...>
22248 <... write resumed> ) = 6400
Rsync aborted because its write to the JungleDisk virtual filesystem
failed with an I/O error. You should look at the JungleDisk logs to
find out why JungleDisk returned the I/O error.
> its says unfinished after every file?
In strace output, "unfinished" after a system call just means that
something happened in another process before the call finished. The
result of the call is given in a subsequent line with "CALL-NAME
resumed". This isn't anything bad.
Matt
More information about the rsync
mailing list