Reference thread at https://lists.freebsd.org/pipermail/freebsd-current/2018-January/068043.html
Not sure this helps: But we have seen this also after system panics
when having soft update journaling enabled. Having soft update journaling
disabled, we do not observed this after several panics.
Just to be clear: The panics are not related to this issue,
but to other network development we do.
Also reproduced on two new installs by my co-op students:
- system panics for some reason, unrelated to filesystems
- fsck SU+J runs after reboot
- kernel reports many cylinder checksum failures
A commit references this bug:
Date: Fri Jan 12 20:25:57 UTC 2018
New revision: 327890
bsdinstall: disable SUJ by default
SUJ + cg checksums produce spurious warnings after an unclean shutdown
(e.g. a crash). For now disable SUJ for UFS installs so installing from
a FreeBSD 12 snapshot results in a usable filesystem, until this can be
Submitted by: Arshan Khanifar <arshankhanifar gmail.com>
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D13890
Please retry with this change included as I believe it will fix the problem.
New Revision: 328092
Correct fsck journal-recovery code to update a cylinder-group
check-hash after making changes to the cylinder group. The problem
was that the journal-recovery code was calling the libufs bwrite()
function instead of the cgput() function. The cgput() function updates
the cylinder-group check-hash before writing the cylinder group.
I tried this patch with success on my laptop! Thank you Kirk :)