Hi all,
I have a solution to my original problem. There are a
couple of observations to make first though -
1. I did go back to 2.3.2 as suggested by Eric and this
did indeed work for me, but my final solution is
different. I tried every version prior to 2.4.6
back to 2.3.2. 2.4.0 - 2.4.6 did not work for me
as per my original email - 2.3.2 did work however.
2. I am doing a local-to-local copy, there is no remote
component in my rsync. Most of the issues that people
are having seem to be with remote rsync.
My solution is simple and may only apply to me, or those
doing local-to-local copies. I went from -
case (a)
--------
/usr/local/bin/rsync -v -v -v -v -v -v -v -v --progress \
--stats --recursive --perms --owner --group --times --sparse \
--one-file-system --delete /mnt/ad2s1e/* /mnt/ad3s1e
to
case (b)
--------
/usr/local/bin/rsync --stats --recursive --perms --owner \
--group --times --sparse --one-file-system \
--delete /mnt/ad2s1e/* /mnt/ad3s1e
and I no longer get the pauses. I left out the multiple
'-v's and --progress and it works. I have tested this back
and forth and confirmed with mtree that (b) works.
I did a little further testing and can confirm that this
works (for me) -
case (c)
--------
/usr/local/bin/rsync -v -v --progress \
--stats --recursive --perms --owner --group --times --sparse \
--one-file-system --delete /mnt/ad2s1e/* /mnt/ad3s1e
Whereas this does not -
case(d)
-------
/usr/local/bin/rsync -v -v -v --progress \
--stats --recursive --perms --owner --group --times --sparse \
--one-file-system --delete /mnt/ad2s1e/* /mnt/ad3s1e
So the addition of the extra '-v' is what kills it for me,
though this works in 2.3.2 for me.
I hope this is a useful info for the developers.
Thanks to Dave for -W and to Eric for suggesting I test
with 2.3.2.
regards
Simon Lai
