On Thu, Dec 8, 2022 at 12:49 PM Kevin Korb wrote:
> The first "Bug Fix" listed in https://rsync.samba.org/ftp/rsync/NEWS#3.2.4 is
> almost certainly related. Apparently it was fixed via remote option but
> since your test doesn't include networking that fix wouldn't help.
>
No, the bug was
Interesting, in that bug the problem was *solved* by adding
--no-whole-file when using --inplace and --sparse, whereas in my case
the problem is *caused* by using --no-whole-file alongside --inplace and
--sparse.
On 08/12/2022 20:48, Kevin Korb via rsync wrote:
The first "Bug Fix" listed in
The first "Bug Fix" listed in
https://rsync.samba.org/ftp/rsync/NEWS#3.2.4 is almost certainly
related. Apparently it was fixed via remote option but since your test
doesn't include networking that fix wouldn't help.
On 12/8/22 15:03, Mark Raymond via rsync wrote:
I believe I have found a
I believe I have found a synchronization bug in rsync. I have a pair of
files, which when synced with||
||
|rsync --no-whole-file --inplace -S|||
||
|are not| identical afterwards. All three options are required, if I
remove any one of the the files sync correctly. I have put the two
files,
