Date: Sat, 25 Nov 2023 09:37:00 +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-GLNPed79XX@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 Rob Norris <robn@despairlabs.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robn@despairlabs.com --- Comment #8 from Rob Norris <robn@despairlabs.com> --- Hi, I'm the author of 15571. Just a couple of notes: - dmu_offset_next_sync=3D0 does appear to be a very reliable workaround, ju= st not technically perfect. Only one person has been able to trip it on an extreme= ly contrived test, as opposed to the default =3D1, which multiple people have = been able to reproduce consistently. - The incorrect dirty check in 12.4 (as in Illumos) is in dmu_object_wait_synced(). I have not explored this at all though; OpenZFS n= ever had this version and a lot has changed since. There may be other reasons wh= y it can't be tripped. Let me know if there's anything I can assist with. Rob. --=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-GLNPed79XX>