better rsync error code when no space?

Ming Zhang blackmagic02881 at gmail.com
Mon Nov 12 16:22:29 GMT 2007


Hi All

I ran into this situation when rsync some files to remote side and
remote file system run out of space.

rsync: writefd_unbuffered failed to write 4 bytes [sender]: Connection
reset by peer (104)
rsync: write failed on "/IMG_5106.JPG" (in dest): No space left on
device (28)

~~~~ no space was detected and reported.


rsync error: error in file IO (code 11) at receiver.c(298)
[receiver=3.0.0pre5]
rsync: connection unexpectedly closed (27 bytes received so far)
[sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[sender=3.0.0pre5]
_exit_cleanup(code=12, file=io.c, line=601): about to call exit(12)


looks like error code 12 is caused by first error, 104.

shall rsync report ENOSPC for this? so it can be much easier to trace
and find out the error.

thanks!

-- 
Ming Zhang


@#$%^ purging memory... (*!%
http://blackmagic02881.wordpress.com/
http://www.linkedin.com/in/blackmagic02881
--------------------------------------------



More information about the rsync mailing list