On Sun, 2009-11-08 at 01:57 -0500, Matt McCutchen wrote: > 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]
I tested commit cece2e3f5e335b8d1bd0862dbc9edbf2d5a4f5dd and the problem is finally fixed: $ rsync-dev big-file small-fs/ rsync: write failed on "/PATH/TO/small-fs/big-file": No space left on device (28) rsync error: error in file IO (code 11) at receiver.c(334) [receiver=3.1.0dev] The output is not as clean as Wayne may have intended for remote pushes and pulls, but at least the critical information is still there: $ rsync-dev localhost:PATH/TO/big-file small-fs/ rsync: write failed on "/PATH/TO/small-fs/big-file": No space left on device (28) rsync error: error in file IO (code 11) at receiver.c(334) [receiver=3.1.0dev] rsync: connection unexpectedly closed (35 bytes received so far) [generator] $ rsync-dev big-file localhost:PATH/TO/small-fs/ rsync: write failed on "/PATH/TO/small-fs/big-file": No space left on device (28) rsync error: error in file IO (code 11) at receiver.c(334) [receiver=3.1.0dev] rsync: [sender] write error: Broken pipe (32) -- 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
