After my OpenBSD 7.2 box lost power, bootup halted when rc ran fsck
which reported problems with inodes. At the root prompt, I ran fsck and
answered 'y' to each prompt. Now, in normal mode, running fsck reports a
few unreferenced files, auto-answers "no" to its "CLEAR?" prompt, and
continues.
$ sudo fsck
...
** /dev/sd0f (1cc70a7feb167ca7.f) (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=1710838 OWNER=root MODE=100444
SIZE=2935688 MTIME=Jan 1 15:44 2023
CLEAR? no
UNREF FILE I=2799427 OWNER=root MODE=100444
SIZE=220408 MTIME=Jan 1 15:44 2023
CLEAR? no
** Phase 5 - Check Cyl groups
16199 files, 373887 used, 14859799 free (447 frags, 1857419 blocks, 0.0%
fragmentation)
...
1 files, 1 used, 1520726 free (14 frags, 190089 blocks, 0.0%
fragmentation)
** /dev/sd0e (1cc70a7feb167ca7.e) (NO WRITE)
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=518412 OWNER=root MODE=100444
SIZE=11479 MTIME=Jan 1 15:44 2023
CLEAR? no
** Phase 5 - Check Cyl groups
404 files, 15061 used, 4232530 free (226 frags, 529038 blocks, 0.0%
fragmentation)
Why does fsck say "NO WRITE" for each partition? Is this why it
auto-answers "no" to the "CLEAR?" question?
--Randall
No comments:
Post a Comment