SUJ issue for stable/10 @r268091

[David Wolfskill]

I rebooted my test machine, and saw:
...
Mounting local file systems:mount: /dev/mfid1: R/W mount of /b denied.
Filesystem is not clean - run fsck. Forced mount will invalidate journal
contents: Operation not permitted
.
Mounting /etc/fstab filesystems failed,  startup aborted
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Jul 14 04:29:19 init: /bin/sh on /etc/rc terminated abnormally, going to
single user mode
Enter full pathname of shell or RETURN for /bin/sh: 
# fsck -p /b && exit || fsck -Cy /b && exit
** SU+J Recovering /dev/mfid1
** Reading 33554432 byte journal from inode 5.
** Building recovery table.
** Resolving unreferenced inode list.
/dev/mfid1: Inode 1099973112 link count 0 invalid
/dev/mfid1: UNEXPECTED SU+J INCONSISTENCY
/dev/mfid1: INTERNAL ERROR: GOT TO reply()
/dev/mfid1: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
** /dev/mfid1

USE JOURNAL? yes

** SU+J Recovering /dev/mfid1
** Reading 33554432 byte journal from inode 5.

RECOVER? yes

** Building recovery table.
** Resolving unreferenced inode list.
Inode 1099973112 link count 0 invalid
UNEXPECTED SU+J INCONSISTENCY

FALLBACK TO FULL FSCK? yes

** Skipping journal, falling through to full fsck

** Last Mounted on /b
** Phase 1 - Check Blocks and Sizes
...
SALVAGE? yes

74628531 files, 1805904798 used, 6705919232 free (27523320 frags, 834799489 blocks, 0.3% fragmentation)

***** FILE SYSTEM STILL DIRTY *****

***** FILE SYSTEM WAS MODIFIED *****

***** PLEASE RERUN FSCK *****
Mounting local file systems:mount: /dev/mfid1: R/W mount of /b denied. Filesystem is not clean - run fsck. Forced mount will invalidate journal contents: Operation not permitted
.
Mounting /etc/fstab filesystems failed,  startup aborted
ERROR: ABORTING BOOT (sending SIGTERM to parent)!
Jul 14 08:05:38 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
Enter full pathname of shell or RETURN for /bin/sh: 
# fsck -p /b && exit || fsck -Cy /b && exit
** SU+J Recovering /dev/mfid1
Journal timestamp does not match fs mount time
** Skipping journal, falling through to full fsck

...


That's not something I'd want to deploy on a couple hundred machines
with the expectation that full fsck is a thing of the past.

How might I gather clues as to what happened (and ini particular, what
went wrong)?

(I'm not subscribed to -fs@; I've set Reply-To as a hint -- thanks!)

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Taliban: Evil cowards with guns afraid of truth from a 14-year old girl.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20140714/510a3d3f/attachment.sig>