Linda Walsh
2012-Oct-11 19:52 UTC
prune empty dirs doesn't seem to be doing so.... && optimizations?
I'm using: (according to ps) /usr/bin/rsync --archive --human-readable --acls --xattrs --hard-links --no-inc-recursive --prune-empty-dirs --whole-file --one-file-system --compare-dest=/home/. --exclude=**/.recycle/** --exclude=CPAN-ishtar-build-cache/** /home/.snapdir/@GMT-2012.10.11-02.23.25/. /home.diff/ But the difference FS systems get a full compliment of every dir in the source. Perhaps it wasn't well tested when using a 3rd dir to compare against? Also, anyway to optimize the same-system case (using shared memory). Also an option to use inode numbers would greatly speed things -- since these are snapshots of each other both file systems will have the same inode numbers for files that equal. As it stands, running the above rsync takes about 90 minutes/invokation. The resulting 'differences' can be copied by "cp" in usually under 1 minute. (a few Gig or less).
Reasonably Related Threads
- [Bug 10748] New: 3.1.0 and 3.1.1 create all dirs on target even with --prune-empty-dirs
- How to net group add 'group' (I scrod myself...can't figure out how descrod)
- rsync 3.0.9 incompatible with self? (proto incompat on local->local)
- --prune-empty-dirs option not doing the job
- snapshot scripts run on linux to allow samba to export Windows "Previous copies" when looking at a network file?