Date: Thu, 19 Mar 2026 10:38:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 293917] zpool with active EDONR checksum can not hold the bootfs Message-ID: <bug-293917-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293917 Bug ID: 293917 Summary: zpool with active EDONR checksum can not hold the bootfs Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: walter.von.entferndt@posteo.net OBSERVED: You can not boot from a zpool with active EDONR checksum. This is not a bug by itself, instead the bug is that it's not documented! There is no notion of this, neither in any zpool-* nor zfs-* manpage. Thank you for reminding us of the meaning of RTFSD ("read the f*ing source, dude!"). So do we have to add a page to the UNIX Haters Handbook? The short documentation of this newly available checksum algorithm sounds appealing, so I guess I'm not the only one who activated it and then had to copy all data twice... EXPECTED: There should be a BIG FAT WARNING in the manpages and any other documentation where the EDONR checksum property is mentioned, that as long as just one single block in the whole pool uses this checksum method -- regardless if it's in the bootfs dataset or any other dataset, volume or snapshot -- renders the whole pool unbootable. Thx in advance for fixing this! -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293917-227>