For the next release, please consider enabling soft update journaling for
– and for
Also, if released before FreeBSD 13.1-RELEASE, https://cgit.freebsd.org/src/commit/?id=fb2feceac34cc9c3fb47ba4a7b0ca31637f8fdf0&h=stable%2F13 to fix fsck_ffs(8).
Thank you for the tip. After a crash, the super fast disk check at reboot:
Starting file system checks:
** SU+J Recovering /dev/gpt/nbsdrootfs
** Reading 33554432 byte journal from inode 5.
** Buiding recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
** 42 journal records in 3584 bytes for 37.50% utilization
** Freed 17 inodes (3 dirs) 507 blocks, and 35 frags.
***** FILE SYSTEM MARKED CLEAN *****
There’s now a schedule for 13.1, the RELEASE of which will include the fix for FreeBSD bug 256746 – fsck_ffs completely broken for background fsck.
https://forums.freebsd.org/posts/554656 includes a link to the schedule, and other information.
My installation on a Kingston USB flash drive suffered a UFS-related kernel panic (bad dir, IIRC) whilst attempting to upgrade packages.
I did not notice a check whilst starting the system. At which point does it become visible?
(GELI-enabled, if that’s relevant.)
As expected, I do have this in dmesg:
WARNING: /data was not properly dismounted