Ryan,
I'm not sure what you expect to happen since for most filesystems
there is no concept of "permission inheritance" in unix-like operating
systems. Rather, newly created files obey the currently set umask (usually
022). Are you saying you want rsync to use your current umask instead
Kevin,
I'm not saying the stat() call is slow or trying to reduce
syscalls. If the quick check fails due to differing timestamps the entire
transfer will be significantly slower because rsync has to defer to the
full checksum algorithm just to find out the files are identical which
m
Marc,
Well you can remove the timestamp checks by adding "--size-only".
If that speeds things up or removes the long "pauses" the timestamps were
to blame. If the behavior is the same then I'm wrong. If I'm right then
you might want to synchronize your clocks or use the " --modify-wind
Alan,
What is the rsync command used? If it hits a large group of files
with no differences (easy to believe across 12TB) but has to compare the
checksums anyways (forced by you or failing the size+time compare) you'll
be I/O bound with almost no corresponding network traffic as it just
Some sshs support the cipher 'none' (-c none). I believe the HPN patches
for ssh have the 'none' cipher patch as well.
Using ssh instead of rsh is still nice since (I believe) even with the
-none cipher you still get an encrypted negotiated username + pass.
Eric Bambach | Discover
Senior Assoc.
Matt,
Its probably not a rsync bug. Its likely that after booting to
create the second image a large number of updates has happened at many
different parts in the filesystem. You may have added only a few MB of
data but a lot of little things are going on in an active system like
files
Group,
I'm having trouble convincing rsync to read and apply ACLs to
files as root or otherwise. Googling, reading the source and docs have not
helped so far. I always seem to get the error message
sys_acl_get_tag_type(): Unsupported attribute value (124).
Our rsync version is
