I had a spontaneous reboot a few days ago, with a -CURRENT from about a week ago. Cause unclear, and I was in X11, which doesn't simplify things. When it came back up, fsck was displeased with the state of the world: ** /dev/ad0s1e ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes 8 DUP I=141 UNEXPECTED SOFT UPDATE INCONSISTENCY 5 DUP I=621 UNEXPECTED SOFT UPDATE INCONSISTENCY ... ** Phase 2 - Check Pathnames DUP/BAD I=621 OWNER=rwatson MODE=100644 SIZE=35491 MTIME=Jun 26 14:13 2003 FILE=/home/rwatson/freebsd/commit/RELENG_4/src/contrib/groff/man/groff_char.man UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? [yn] y ... ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts BAD/DUP FILE I=141 OWNER=rwatson MODE=100444 SIZE=1155 MTIME=Oct 24 19:34 2004 CLEAR? [yn] n ... What's odd here is that these files hadn't been touched in a week. I'm going to upgrade my notebook to a known source configuration (things a bit indeterminate here since I had a lot of local patches in odd places) and see about reproducing. Has anyone else seen this out of fsck? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert_at_fledge.watson.org Principal Research Scientist, McAfee ResearchReceived on Wed Nov 03 2004 - 10:16:16 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:20 UTC