diff options
| author |   Sam James <sam@gentoo.org> | 2023-11-24 21:48:39 +0000 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2023-11-24 21:51:35 +0000 |
| commit | ea74809fc56791c2f45fc46815a7d5a8fd462961 (patch) | |
| tree | dd24320a39f1732a8643a1fb80ad3d99360d6302 /sys-fs/zfs-kmod/zfs-kmod-9999.ebuild | |
| parent | sci-libs/lapack: add 3.12.0 (diff) | |
| download | gentoo-ea74809fc56791c2f45fc46815a7d5a8fd462961.tar.gz gentoo-ea74809fc56791c2f45fc46815a7d5a8fd462961.tar.bz2 gentoo-ea74809fc56791c2f45fc46815a7d5a8fd462961.zip | |
sys-fs/zfs-kmod: disable zfs_dmu_offset_next_sync tunable by default
As a mitigation until more is understood and fixes are tested & reviewed, change
the default of zfs_dmu_offset_next_sync from 1 to 0, as it was before
05b3eb6d232009db247882a39d518e7282630753 upstream.
There are no reported cases of The Bug being hit with zfs_dmu_offset_next_sync=1:
that does not mean this is a cure or a real fix, but it _appears_ to be at least
effective in reducing the chances of it happening. By itself, it's a safe change
anyway, so it feels worth us doing while we wait.
Note that The Bug has been reproduced on 2.1.x as well, hence we do it for both
2.1.13 and 2.2.1.
Bug: https://github.com/openzfs/zfs/issues/11900
Bug: https://github.com/openzfs/zfs/issues/15526
Bug: https://bugs.gentoo.org/917224
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'sys-fs/zfs-kmod/zfs-kmod-9999.ebuild')
| -rw-r--r-- | sys-fs/zfs-kmod/zfs-kmod-9999.ebuild | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sys-fs/zfs-kmod/zfs-kmod-9999.ebuild b/sys-fs/zfs-kmod/zfs-kmod-9999.ebuild index 0b3c28a2134c..6537bbc1a148 100644 --- a/sys-fs/zfs-kmod/zfs-kmod-9999.ebuild +++ b/sys-fs/zfs-kmod/zfs-kmod-9999.ebuild @@ -60,6 +60,7 @@ PDEPEND="dist-kernel? ( ~sys-fs/zfs-${PV}[dist-kernel] )" PATCHES=( "${FILESDIR}"/${PN}-2.1.11-gentoo.patch + "${FILESDIR}"/${PN}-2.2.1-Disable-zfs_dmu_offset_next_sync-tunable-by-default.patch ) pkg_pretend() { |