[Bug 2044657] Re: zfs block cloning file system corruption

[Mike Ferreira]

@toekneefan -- Our tests of 2.2.1 from Noble Proposed showed that it was
actually "enabled" by default, instead of being disabled like they said
they did in it's release notes... So the rpool installs as "active", and
any other pools created with feature=default (or just omitted) are
created as that being "enabled"... So assuming that was turned off,
turned out to be wrong.

The only way I got that feature to create new pools with
feature at block_cloning=disabled, was to explicitly pass that in the
creation statement.

The Canonical 'ubuntu-desktop-installer' team needs to know they need to
add option that to the ZFS scripted installer script... In my debug
traces during the install, they are passing "features=default"... If
that feature does need to be turned off.

I guess that only really matters if these patches for the Bug works and
prevents it when they hit us and are applied. That "is" why turning off
that feature was done for the meantime.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2044657

Title:
  zfs block cloning file system corruption

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  OpenZFS 2.2 reportedly has a bug where block cloning might lead to
  file system corruption and data loss. This was fixed in OpenZFS 2.2.1.

  Original bug report: https://github.com/openzfs/zfs/issues/15526

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044657/+subscriptions