I do backups using rsync, and - every so often - a file takes far longer
than it normally does. These are large data files which typically change
only a little over time.
I'm guessing that these large transfers are caused by occasional changes
that break (ie. yield poor performance) in the
On Sun, 2009-11-29 at 16:07 +, Andrew Gideon wrote:
Is
there some way to run rsync in some type of dry run mode but where an
actual determination of what pages should be copied is performed?
The current --dry-run doesn't go down to this level of detail as far as I
can see. It
I can't answer your question directly, but I can say that
it is not strictly the number of bytes that are different
that matters, but also how the differences are distributed
in the file. Unless you explicitly set the block size,
rsync uses a size that is the sqrt of the size of the
file, thus
Once upon a time, Matt McCutchen m...@mattmccutchen.net said:
---
generator.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
Hmm, I've applied this patch on both sides, but I'm still getting the
same error. Is this because I'm using fake-super only on one side?
# rsync -v
On Sun, Nov 29, 2009 at 5:26 PM, Chris Adams cmad...@hiwaay.net wrote:
Hmm, I've applied this patch on both sides, but I'm still getting the
same error.
The errors should go away on the next run, since rsync should have set u+rwx
on the dirs during the most recent run (but it doesn't do it
Once upon a time, Wayne Davison way...@samba.org said:
On Sun, Nov 29, 2009 at 5:26 PM, Chris Adams cmad...@hiwaay.net wrote:
Hmm, I've applied this patch on both sides, but I'm still getting the
same error.
The errors should go away on the next run
No, the errors went away when I
