Date: Sat, 2 Dec 2023 12:14:19 +0100 (GMT+01:00) From: Alexander Burke <alex@alexburke.ca> To: Thomas Zander <riggs@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Errata Notice FreeBSD-EN-23:16.openzfs Message-ID: <d722ebbc-6ef4-413f-8483-50ba125ff768@alexburke.ca> In-Reply-To: <ZWsI4SbNU2xPjaPF@marvin.hueftgold.tld> References: <20231201031737.DF0231B942@freefall.freebsd.org> <ZWsI4SbNU2xPjaPF@marvin.hueftgold.tld>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, `zpool scrub` will not catch this issue as the corruption did not happen on= disk. Solutions are being researched on the OpenZFS GitHub issue tracker regardin= g pools which may have already experienced the issue. Cheers, Alex ---------------------------------------- Dec 2, 2023 11:37:37 Thomas Zander <riggs@freebsd.org>: > On Fri, Dec 01, 2023 at 03:17:37AM +0000, FreeBSD Errata Notices wrote: >=20 >> Topic:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 OpenZFS dat= a corruption >> ... >> I.=C2=A0=C2=A0 Background >> II.=C2=A0 Problem Description >> III. Impact >> IV.=C2=A0 Workaround >> V.=C2=A0=C2=A0 Solution >=20 > IMHO, what is missing between sections III and IV when the bug is about > persistency (file systems, data storage, file format conversion, ...) > is a subsection "Is there a way to find out which files are affected?" >=20 > For eaxmple, in the case of ZFS, it would be helpful to answer "Will > 'zpool scrub' find and / or repair affected files?" >=20 > There will be cases (this one? I don't know. Anyone?) in which the > answer is unfortunately "Nope, sorry.", but this would still be helpful > information, since it would save people from browsing the net for > hours, looking for an answer to that question. >=20 > Thanks for considering for future errata > Riggs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d722ebbc-6ef4-413f-8483-50ba125ff768>