This affects me as well.
All though this seems to be working
apt policy zfs-dkms
zfs-dkms:
Installed: 2.2.0-0ubuntu3
Candidate: 2.2.0-0ubuntu3
Version table:
2.2.1-0ubuntu1 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64
Packages
100 http://archive.ubuntu.com/ubuntu noble-proposed/universe i386
Packages
*** 2.2.0-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu noble/universe i386 Packages
100 /var/lib/dpkg/status
Please also follow the Link Mike provided
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044969
Title:
Upstream bug: ZFS feature@block_cloning causes data corruption
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
Noble DAILY ISO 2023.11.27 & Current Mantic Installers.
some copied files are corrupted (chunks replaced by zeros) ISSUE #15526
RE:https://github.com/openzfs/zfs/issues/15526
zpool feature@block_cloning came out with version 2.2.0 of zfs-linux,
this is not the root of that bug, but exacerbates the underlying bug.
The bug was reported, and version 2.2.1 was released with that feature
turned off by default, so that would be a problem out of the gate.
There is a patch out which got approved, merged and built tonight that, after
testing, seems to correct that:
dnode_is_dirty: check dnode and its data for dirtiness #15571
https://github.com/openzfs/zfs/pull/15571
Unfortunately, Mantic was released with version 2.2.0. Current DEV
Noble also has 2.2.0. This feature in the default ZFS install scripts
for both Mantic and Noble, with the current default, In bpool,
feature@block_cloning is disable, but for rpool, the same feature is
enabled, so "at risk".
This feature is set at pool creation time. You cannot set this feature
to disable without destroying the pool and recreating it fresh. Have
good backups, via rsync. cp is affected, but not rsync.
Version 2.2.1 has this feature disabled by default. It was released
Nov 21, 2023.
I am proposing that the patched build from tonight get pushed through
for Mantic when it hits from upstream... And possibly pushing 2.2.1
through for Noble, where we can thoroughly test it in this current DEV
Cycle.
Also, this was filed because of Security as it relates to data integrity
concerns:
CVE-2023-49298
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-49298
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: zfsutils-linux 2.2.0-0ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Nov 27 19:58:32 2023
InstallationDate: Installed on 2023-11-23 (4 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231123)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
