On Sat, 2009-11-07 at 09:38 -0800, Wayne Davison wrote: > On Wed, Nov 4, 2009 at 8:05 PM, Matt McCutchen > <m...@mattmccutchen.net> wrote: > > With commit 84c11e85a4c4a12ecacba24afe9617222e4361e6, I get > different > > output, but still not the desired "No space left on device": > > > Yeah, that's the long-standing issue where a fatal error on the server > side can cause the client side to get a socket error trying to write > to the socket before it has a chance to read the error(s) from the > socket. The latest git archive finally has a fix for this.
I tested commit 2907af472d1f33b3c422cb9f601c121b242aa9c7 and, again, the output is different but the problem is not fixed: $ rsync-dev big-file small-fs/ rsync: connection unexpectedly closed (146 bytes received so far) [sender] $ rsync-dev --msgs2stderr big-file small-fs/ rsync: write failed on "/PATH/TO/small-fs/big-file": No space left on device (28) rsync: connection unexpectedly closed (36 bytes received so far) [sender] rsync error: error in file IO (code 11) at io.c(181) [receiver=3.1.0dev] -- Matt -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html