Date: Thu, 30 Nov 2023 18:59:34 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 275308] EN tracking issue for potential ZFS data corruption Message-ID: <bug-275308-3630-IVH1MTrxV2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275308-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-275308-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275308 --- Comment #28 from Ed Maste <emaste@freebsd.org> --- (In reply to mike from comment #27) The workaround actually improves performance (at the cost of possibly incor= rect hole reporting). Once the update is applied though I believe there's no benefit (from a risk mitigation perspective) in keeping the workaround. I've added a sentence to= the end of the workaround section in the draft EN: IV. Workaround Setting the vfs.zfs.dmu_offset_next_sync sysctl to 0 disables forcing TXG sync to find holes. This is an effective workaround that greatly reduces the likelihood of encountering data corruption, although it does not completely eliminate it. Note that with the workaround holes will not be reported in recently dirtied files. See the zfs(4) man page for more information of the impact of this sysctl setting. The workaround should be removed once the system is updated to include the fix described in this notice. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275308-3630-IVH1MTrxV2>