> Date: Wed, 20 Jan 2016 23:04:20 -0800
> From: Wayne Davison
> On Thu, Dec 25, 2014 at 2:48 AM, Ingo Br=C3=BCckl
wrote:
> > On systems using nanoseconds differences should be taken into
> > consideration.
> The problem is that if you transfer from a filesystem that ha
Hi, I filed bug 11521 [1] back in August, and I can't tell if anyone's
looked at it.
It is a pretty rare, but easy to understand problem, with (I think) a
straightforward fix.
I included a reproducer script and a patch that worked well for me, but as
this is the first time I've looked at the rsyn
On 2016-01-21 15:00, Kevin Korb wrote:
> First, don't use -z on a local copy. It will only make rsync slower
> for no reason at all.
Thanks. Hadn't thought about that. I just copied most from the spelled
out "archive" list of switches. But is rsync so "stupid" that it really
considers z for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, don't use -z on a local copy. It will only make rsync slower
for no reason at all.
Second, 45 million files means 90 million calls to stat(). This will
take a while even if nothing needs copying.
On 01/21/2016 03:20 AM, dbonde+forum+rsync.li
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 mem
