exit status 13 in version 3.1

[Matt McCutchen]

On Wed, 2009-11-04 at 08:39 -0800, Wayne Davison wrote:
> On Tue, Nov 3, 2009 at 9:25 AM, Matt McCutchen
> <matt at mattmccutchen.net> wrote:
>         rsync error: errors with program diagnostics (code 13) at
>         log.c(340) [sender=3.1.0dev]
> 
> This means that you didn't update recently.  Sadly, it appears my
> reply mentioning that I fixed the problem only went to Carlos, and
> missed the list.  Here it is:
> 
> Wayne said:
>         That is likely to have been caused by the code going into
>         --msgs2stderr mode when it gets a socket error, but rwrite()
>         couldn't handle some of the more esoteric error codes (because
>         they don't normally make it that far without being transformed
>         into a simpler code).  I've checked in a fix for this.
> 
> If you would, please re-check your disk-overflow test case with the
> latest code (and --msgs2stderr turned off) and see if that gets the
> error to you.

With commit 84c11e85a4c4a12ecacba24afe9617222e4361e6, I get different
output, but still not the desired "No space left on device":

$ rsync-dev big-file small-fs/
rsync: write error: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(756) [sender=3.1.0dev]
$ rsync-dev --msgs2stderr 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: write error: Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(756) [sender=3.1.0dev]

-- 
Matt