https://bugzilla.samba.org/show_bug.cgi?id=11651
--- Comment #1 from Peter Wu <pe...@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 https://git.samba.org/rsync.git/?p=rsync.git;a=commitdiff;h=cfce9f6dc353a013ab8d07c20a392aeaf6cab5ea 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 --sparse[=always]? -- You are receiving this mail because: You are the QA Contact for the bug. -- 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
