rsync - Sep 2004 - [PATCH] Inplace option for rsync

Mark,

The patch seems to cause problems if there are any transfer
interruptions (as mentioned in the comments in the patch). However, even
on a retransfer, the earlier partially transferred file is not fixed,
although the client appears to think the transfer has completed
successfully. This appears to be a serious bug.

Note: Both client and server have the inplace patch, and on Linux
platforms WS 3.

Raj

On Mon, Sep 13, 2004 at 09:31:02AM -0700, Raghu Kulkarni
wrote:
> However, even on a retransfer, the earlier partially transferred file
> is not fixed, although the client appears to think the transfer has
> completed successfully.
Do you mean the file does not transfer again (meaning that rsync thinks
the files are the same based on timestamp and size) or that rsync
transmits the file on the next run, but it doesn't update correctly?
The first shouldn't happen unless the source file got modified exactly
when the destination file was being written (in which case you'd need to
use -c to tell rsync to check if it is really different or not).  The
latter would indicate a serious bug, but one that has nothing to do with
the transfer being interrupted (since a transfer is a transfer).  If you
have seen the latter problem, please preserve both the source and
destination file and either (if possible) make them available to me for
testing or keep them around to facilitate future testing.

..wayne..