File changed during save....

devzero at web.de devzero at web.de
Sun Sep 16 22:10:20 GMT 2007


> Note that back-to-back rsyncs make the window of opportunity much
> much smaller for things to change during transit.

yes, but it still leaves room for corrupted transfers nobody would probably know about !?


> -----Ursprüngliche Nachricht-----
> Von: <tony at servacorp.com>
> Gesendet: 16.09.07 18:24:23
> An:  "'roland'" <devzero at web.de>
> CC: <rsync at lists.samba.org>
> Betreff: RE: File changed during save....


> 
> Matt McCutchen wrote:
> > 
> > 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
> > -- 
> 
> Note that back-to-back rsyncs make the window of opportunity much
> much smaller for things to change during transit.
> 
> 


______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!		
Jetzt testen! http://produkte.web.de/club/?mc=021130



More information about the rsync mailing list