File changed during save....

[devzero at web.de]

> Handling of concurrent changes to source files is one of rsync's
> weaknesses.  

too bad, but good to know :)

>The rsync sender naively reads each source file from
> beginning to end and sends what it sees; it doesn't detect if source
> files change while being transferred.  

that`s what i feared.

> In many cases, the concurrent
> modification will leave the source file with an mtime different from
> the mtime rsync saw when it statted the file during file-list building
> (which gets set on the destination file), 
>so a subsequent rsync run will fix the corrupted destination file.  

mhh - if the file being very large and stat`ed  before transfer and
then changing during transfer because that file is accidentally in 
use (how should the receiver/sender always know?) - how should 
a subsequent rsync run be able to fix this reliably ? the next run, 
rsync would detect that it changed and would transfer the differences 
again - and while doing this, the file could change again....and so on......
so, this is not a reliable workaround, imho.

what about thinking about an option for stat`ing the file _after_ transfer
again, so rsync could at least tell "warning: file changed during rsync 
transfer...." which would be better than nothing, imho.

>See this thread for more information:
> http://lists.samba.org/archive/rsync/2006-January/014534.html

thanks for the pointer

roland

ps:
sorry, couldn`t cc to hashproduct+rsync at gmail.com - my webmailer won`t let me


> -----Ursprüngliche Nachricht-----
> Von: "Matt McCutchen" <hashproduct+rsync at gmail.com>
> Gesendet: 16.09.07 17:56:45
> An: roland <devzero at web.de>
> CC: rsync at lists.samba.org
> Betreff: Re: File changed during save....


> 
> On 9/15/07, roland <devzero at web.de> wrote:
> > what`s the rsync equivalent to this?
> > how can i see which files changed while rsync was transferring them ?
> 
> Handling of concurrent changes to source files is one of rsync's
> weaknesses.  The rsync sender naively reads each source file from
> beginning to end and sends what it sees; it doesn't detect if source
> files change while being transferred.  In many cases, the concurrent
> modification will leave the source file with an mtime different from
> the mtime rsync saw when it statted the file during file-list building
> (which gets set on the destination file), so a subsequent rsync run
> will fix the corrupted destination file.  See this thread for more
> information:
> 
> http://lists.samba.org/archive/rsync/2006-January/014534.html
> 
> Matt
> 


_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220