[Bug 11651] Can we allow --inplace and --sparse to coexist when --whole-file is in play?

samba-bugs at samba.org samba-bugs at samba.org
Sat Feb 13 11:55:26 UTC 2016


--- Comment #1 from Peter Wu <peter at lekensteyn.nl> ---
What is the technical limitation exactly? Different transfer algorithms? This
comes from OLDNEWS:

 - Reject the combination of --inplace and --sparse since the sparse-output
   algorithm doesn't work when overwriting existing data.

The --inplace --sparse combination was rejected since

For a local full system backup, I would prefer a best-effort transfer where 99%
of all files are copied with --inplace (such that btrfs COW still works) while
that single sparse Docker file of 100G (in reality 0 bytes) does not eat all
space (apply --sparse).

Would that be a possibility? Maybe a --sparse=try option besides

You are receiving this mail because:
You are the QA Contact for the bug.

More information about the rsync mailing list