Good day, all.
I've got a dozen problems with my servers on the FreeBSD (9.0 and later) with turned on journaling with SoftUpdates on root slice (/). The problem is what filesystem stay inconsistently after hard reboot and fsck completed check filesystem with journaling use. Althrough it says filesystem is clean, it's not. In the worse case it leads to the reset loop (FreeBSD can't boot after single mode due filesystem is bad). The only way to fix it is to boot in single-user mode and start fsck twice. For example, one of the my server currently under threat (check from "work" mode):
[CMD=""]tunefs -p /[/CMD]
[CMD=""]uname -a[/CMD]
And that problem isn't unitary.
What's the caveat?
I've got a dozen problems with my servers on the FreeBSD (9.0 and later) with turned on journaling with SoftUpdates on root slice (/). The problem is what filesystem stay inconsistently after hard reboot and fsck completed check filesystem with journaling use. Althrough it says filesystem is clean, it's not. In the worse case it leads to the reset loop (FreeBSD can't boot after single mode due filesystem is bad). The only way to fix it is to boot in single-user mode and start fsck twice. For example, one of the my server currently under threat (check from "work" mode):
[CMD=""]tunefs -p /[/CMD]
Code:
tunefs: POSIX.1e ACLs: (-a) disabled
tunefs: NFSv4 ACLs: (-N) disabled
tunefs: MAC multilabel: (-l) disabled
tunefs: soft updates: (-n) enabled
tunefs: soft update journaling: (-j) enabled
tunefs: gjournal: (-J) disabled
tunefs: trim: (-t) disabled
tunefs: maximum blocks per file in a cylinder group: (-e) 4096
tunefs: average file size: (-f) 16384
tunefs: average number of files in a directory: (-s) 64
tunefs: minimum percentage of free space: (-m) 8%
tunefs: optimization preference: (-o) time
tunefs: volume label: (-L)
# fsck /
Code:
** /dev/label/rootfs (NO WRITE)
USE JOURNAL? no
** Skipping journal, falling through to full fsck
SETTING DIRTY FLAG IN READ_ONLY MODE
UNEXPECTED SOFT UPDATE INCONSISTENCY
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
126143 files, 1169116 used, 7085540 free (5004 frags, 885067 blocks, 0.1% fragmentation)
[CMD=""]uname -a[/CMD]
Code:
FreeBSD leht 9.0-RELEASE FreeBSD 9.0-RELEASE #1: Fri Mar 16 05:08:15 MSK 2012 root@bsd9:/usr/obj/usr/src/sys/ROUTER_HOME_NETS amd64
And that problem isn't unitary.
What's the caveat?