>From the rsync mailing list archive: Simon Lai wrote:
> I'm using rsync to keep two local 30G disk partitions,
> in sync. This *use to* work fine, but now rsync stops
> after 500 - 800 files. Some environmental info follows,
> some of this may be superfluous, but maybe not ..
...
> /dev/ad2s1e 29719055 2685409 26736456 9% 27981 437937 6% /mnt/ad2s1e
> /dev/ad3s1e 29719055 2683507 26738358 9% 31956 433962 7% /mnt/ad3s1e
...
> /usr/local/bin/rsync -v -v -v -v -v -v -v -v --progress --stats
> --timeout=5 --recursive --perms --owner --group --times --sparse
> --one-file-system --delete /mnt/ad2s1e/* /mnt/ad3s1e
Hold on, you're not even going over a network, just using local disks. All
the changes that had to do with hanging was supposed to have only affected
networking.
It doesn't even really make sense to use rsync for this purpose, becaues
the "rsync algorithm" is optimized for *low-bandwidth* between the
endpoints. RAM on a single machine is the ultimate high bandwidth I would
say. You should probably use --whole-file (-W) to disable the rsync
algorithm and just take advantage of rsync's convenient copying features
(especially the skipping of files whose timestamps haven't changed).
- Dave Dykstra
