Rsync 3.0.5pre2 released
buraphalinuxserver at gmail.com
Sun Nov 16 05:49:50 GMT 2008
Trying rsync 3.0.5pre2 from ext3 on lvm2 on md to USB thumb drive
still fails, but has a different message now:
rsync -rltpvxH --progress --delete /data/bls1.2/dvd/source .
(lots of success, but then this)
32768 8% 0.00kB/s 0:00:00
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
File-list index 0 not in 151 - 1874 (finish_hard_link) [generator]
rsync error: protocol incompatibility (code 2) at rsync.c(647)
rsync: connection unexpectedly closed (9164 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at
Since the rsync is going from one place on the machine to another
without using the network, I fail to understand how a protocol failure
On 11/16/08, Wayne Davison <wayned at samba.org> wrote:
> Rsync version 3.0.5pre2 is now available for release testing. This is
> a bug-fix release.
> I hope this is the final pre-release for 3.0.5, so please test this new
> release and send email to the rsync mailing list with any questions,
> comments, or bug reports.
> The changes since 3.0.5pre1:
> - Fixed the use of a dot-dir path (e.g. foo/./bar) inside a --files-from
> file when the root of the transfer isn't the current directory.
> - Fixed a bug with "-K --delete" removing symlinks to directories when
> incremental recursion is active.
> - Fixed a hard to trigger hang when using --remove-source-files.
> - Fixed reverse lookups in the compatibility-library version of
> - Fixed a bug when using --sparse on a sparse file that has over 2GB of
> consecutive sparse data.
> - Got rid of a bunch of "warn_unused_result" compiler warnings.
> - If an ftruncate() on a received file fails, it now causes a partial-
> transfer warning.
> - A couple manpage improvements.
> - Allow a path with a leading "//" to be preserved (CYGWIN only).
> To see a full summary of the changes since 3.0.4, visit this link:
> You can download the source tar file and its signature from here:
> The patches directory is now in a separate tar file (for those that want
> one or more of the patches):
> See the rsync website for other download methods, including diffs, etc.:
More information about the rsync