[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
*** This bug is a duplicate of bug 2044657 *** https://bugs.launchpad.net/bugs/2044657 ** This bug has been marked a duplicate of bug 2044657 zfs block cloning file system corruption -- 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
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
zfs-linux 2.2.2 released tonight... In the changelog: dnode_is_dirty: check dnode and its data for dirtiness #15571 #15526 Which is the above patch for CVE 2023-49298 -- 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
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
To install 2.2.1, i had to enable proposed in sources, then explicitly install: >>> sudo apt install -y zfsutils-linux=2.2.1-0ubuntu1 libnvpair3linux=2.2.1-0ubuntu1 libuutil3linux=2.2.1-0ubuntu1 libzfs4linux=2.2.1-0ubuntu1 libzpool5linux=2.2.1-0ubuntu1 zfs-dkms=2.2.1-0ubuntu1 >>> To get all the dependencies. I did tha before the install of Noble, then again after the install to reinstall what it rsync'ed from the Snap image to /target, so they would be 2.2.1. But there is still something wrong with that. Debuggin whta is being passed... >>> # Autogenerated by Subiquity: 2023-11-29 04:40:40.713721 UTC install: error_tarfile: /var/log/installer/curtin-errors.tar ... storage: config: ... - vdevs: - partition-3 pool: rpool mountpoint: / pool_properties: ashift: 12 autotrim: 'on' version: null fs_properties: acltype: posixacl atime: null canmount: 'off' compression: lz4 devices: 'off' dnodesize: auto normalization: formD relatime: 'on' sync: standard xattr: sa default_features: true id: zpool-1 type: zpool - pool: zpool-1 volume: ROOT properties: canmount: 'off' mountpoint: none id: zfs-2 type: zfs ... >>> You can see that it says: "default_features: true" But the zpool property feature@block_cloning is still returning as "active" <-- Which is strange, because that should say either "enabled" or "disabled"... To confirm, with everything as 2.2.1, hwere OpenZFS siad that that feature is specifically 'disabled', I created another pool, and it was "enabled" by default. I had to destroy the zpool and explicitly tell it to be disabled in the creation statement. -- 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
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
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
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- 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
[Kernel-packages] [Bug 2044969] Re: Upstream bug: ZFS feature@block_cloning causes data corruption
** Information type changed from Private Security to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-49298 -- 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: New 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
