Date: Mon, 24 Apr 2023 15:46:24 -0700 From: Pete Wright <pete@nomadlogic.org> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: current status of zfs block_cloning on CURRENT? Message-ID: <4f9470a0-4f14-a31b-52a9-7746d6fa09e6@nomadlogic.org>
next in thread | raw e-mail | index | archive | help
hi everyone, i've seen a few threads about the block_cloning feature causing data corruption issues on CURRENT and have been keen to avoid enabling it until the dust settles. i was under the impression that we either reverted or disabled block_cloning on CURRENT, but when i ran "zpool upgrade" on a pool today it reported block_cloning was enabled. this is on a system i rebuilt yesterday. i was hoping to get some clarity on the effect of having this feature enabled, is this enough to trigger the data corruption bug or does something on the zfs filesystem itself have to be enabled to trigger this? i also noticed there is no entry for this feature in zpool-features(7), hence i thought i was safe to upgrade my pool. thanks in advance, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f9470a0-4f14-a31b-52a9-7746d6fa09e6>