Sent from my iPad
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You might find the lsh program in the support dir of the source tree
useful. It is essentially the same as using ssh localhost but without
the overhead.
On 05/22/13 17:25, Allen Supynuk wrote:
> Sorry for the churn and thanks for the suggestions. Whe
Sorry for the churn and thanks for the suggestions. When I redid my
experiments over the network everything worked just as I dreamed it
would. Changing the first 4K bytes only caused a 4K change in the
copy. Changing meta-data (time stamp) only caused the time stamp to
change in the copy.
This is
Kevin,
I will try again over a remote connection to see if that makes a
difference. Not expecting -z to day much of anything based on the
random data, just wanting to be consistent with the flags in the
finished solution.
Chris,
You only get --whole-file if you specify it (or -W).
Paul,
For my
On Tue 21 May 2013, Allen Supynuk wrote:
>
> ## 1) Start with an empty filesystem
>
> $ df -h .
Note that you need to be using "btrfs filesystem df ."
for reliable numbers; the normal df does not take into account
background cleanups etc.
Paul
--
Please use reply-all for most replies to avoid
On 2013-05-21, Allen Supynuk wrote:
> I have been doing some experiments with rsync on btrfs, a
> copy-on-write file system that is approaching or having just achieved
> production-ready status depending on your requirements.
> ## 6) Use rsync --inplace to make a copy of the first file.
> ##
I have been doing some experiments with rsync on btrfs, a
copy-on-write file system that is approaching or having just achieved
production-ready status depending on your requirements.
For my purposes the reliability appears by almost all accounts to be
there, and the compression alone makes it ver
