search for: dscf0748

...examination I found at least one problem with this transfer (that is still running): hard links are not preserved: This is how a certain file looks at the source where it is backed up on several locations using hard links: source volume: zsh-% ls -i "/…/backups/2011-06-23-040258/Pictures/DSCF0748.JPG" 9236871 /…/backups/2011-06-23-040258/Pictures/DSCF0748.JPG zsh-% ls -i "/…/backups/2010-12-18-070445/Pictures/DSCF0748.JPG" 9236871 /…/backups/2010-12-18-070445/Pictures/DSCF0748.JPG destination volume: zsh-% ls -i "/…/backups/2011-06-23-040258/Pictures/DSCF0748.JPG&quo...

I run a rsync job transferring about 45 million files/approximately 1.8 TB data (a Mac OS X Time Machine backup) over a 100 MBit connection. I use rsync 3.1.1 from MacPorts (I first tried the built in rsync, version 2.6.9, since it has a Mac OS X specific cache parameter, but it ran out of memory) with the following parameters % rsync -HzvhErlptgoDW --stats --progress --out-format="%t %f

...ith > this transfer (that is still running): hard links are not > preserved: > > This is how a certain file looks at the source where it is backed > up on several locations using hard links: > > source volume: > > zsh-% ls -i "/…/backups/2011-06-23-040258/Pictures/DSCF0748.JPG" > 9236871 /…/backups/2011-06-23-040258/Pictures/DSCF0748.JPG > > zsh-% ls -i "/…/backups/2010-12-18-070445/Pictures/DSCF0748.JPG" > 9236871 /…/backups/2010-12-18-070445/Pictures/DSCF0748.JPG > > > destination volume: > > zsh-% ls -i "/…/back...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I need to know what the paths were so I know how they relate to the file names you listed. On 01/23/2016 05:10 PM, dbonde+forum+rsync.lists.samba.org at gmail.com wrote: > On 2016-01-23 22:59, Kevin Korb wrote: >> I want to know what your whole command line was so I can >> understand your results. > > % rsync -HzvhErlptgoDW

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As long as it still sees both links it is fine. Essentially, the way it works is that whenever rsync -H (on the source) sees a file with a link count >1 it remembers the inode#>filename pair. If it finds another instance of that inode it then links to the same file on the target. So, if you abort after it copies one but before it links the

...>> analyzing them together. > > I'm not sure I understand your answer. As you could see in my > previous message, the files that should be linked but was > duplicated was located in the same root directory ("/backups"): > > /backups/2011-06-23-040258/Pictures/DSCF0748.JPG" > > > /backups/2010-12-18-070445/Pictures/DSCF0748.JPG" > > Why is rsync losing track of the links just because the transfer > was interrupted if your explanation is correct? > - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-...

...m wrote: > On 2016-01-23 23:24, Kevin Korb wrote: >> I need to know what the paths were so I know how they relate to >> the file names you listed. > > I posted the relevant parts of the path in a previous message > > /Volumes/A/Backups.backupdb/mm/2011-06-23-040258/path/DSCF0748.JPG > /Volumes/B/Backups.backupdb/mm/2011-06-23-040258/path/DSCF0748.JPG > > The only difference is the name of the volume, A and B, above. > - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone: (407)...