On 14/02/2023 06:12, Paul Eggert wrote:
On 2023-02-13 09:16, George Valkov wrote:
1. We apply my original patch to disable sparse-copy on macOS. Otherwise since
fclonefileat is not used whenever we overwrite a file, corruption will still
occur.
I'm not entirely sold on this patch, because I
> On 2023-02-14, at 8:12 AM, Paul Eggert wrote:
>
> On 2023-02-13 09:16, George Valkov wrote:
>> 1. We apply my original patch to disable sparse-copy on macOS. Otherwise
>> since fclonefileat is not used whenever we overwrite a file, corruption will
>> still occur.
>
> I'm not entirely sold
On 2023-02-13 09:16, George Valkov wrote:
1. We apply my original patch to disable sparse-copy on macOS. Otherwise since
fclonefileat is not used whenever we overwrite a file, corruption will still
occur.
I'm not entirely sold on this patch, because I still don't understand
what's
On 2023-02-14 04:12, Pádraig Brady wrote:
I suspect it's a similar issue to the one that openzfs had:
https://github.com/openzfs/zfs/issues/11900
Yes, quite likely.
Given how closed / uncommunicative Apple are in general
and specifically for this already reported bug,
I'm inclined to
