[URGENT] Bug discovered in OpenZFS vs. 2.2.0

[nixota]

Hello everyone,

I re-post here the call for action due to a bug discovered in OpenZFS vs. 2.2.0 by the Gentoo team:

https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1

Gentoo users have identified a block cloning bug (https://github.com/openzfs/zfs/issues/15526) that can result in data corruption in zfs-2.2.0. To workaround this, zfs-2.2.1 disables block cloning by default (see https://github.com/openzfs/zfs/pull/15529 and https://github.com/openzfs/zfs/commit/479dca51c66a731e637bd2d4f9bba01a05f9ac9f).

It gets recommended to update to vs. 2.2.1 ASAP.

BR
N.

[lundman]

Oh I have been keeping an eye on the progress on that bug. Do we know if the macOS version is affected by it at all? We do
lag behind their master a little, and block cloning is not used by default.

[lundman]

I am unable to reproduce it so far, but they appear to have a work around, so if you
are concerned, it could be worth considering:

https://github.com/openzfs/zfs/issues/15526

macOS:
sysctl kstat.zfs.darwin.tunable.zfs.dmu_offset_next_sync=0

[nixota]

Thank You very much. I'll check that out.

Best Regards.

[philk]

macOS:
sysctl kstat.zfs.darwin.tunable.zfs.dmu_offset_next_sync=0

Thank you! Unfortunately I don't have this tunable on Mojave with zfs-macOS-2.1.0-1, and the bug seems to affect it as well:

Code: Select all

sysctl: unknown oid 'kstat.zfs.darwin.tunable.zfs.dmu_offset_next_sync'