How to use fsck ?

[hushcoden]

After a sudden outage, I've run the command fsck:

Code: [Select]

root@hush:/ # fsck
** /dev/gpt/rootfs (NO WRITE)
** Last Mounted on /mnt
** Root file system
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=2006612 (20672 should be 20608)
CORRECT? no

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE  I=2007178  OWNER=root MODE=100644
SIZE=197 MTIME=Mar 20 12:22 2021
RECONNECT? no


CLEAR? no

** 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

71680 files, 1015643 used, 26972945 free (4945 frags, 3371000 blocks, 0.0% fragmentation)
root@hush:/ #
Is there anything to worry about? How to correct the block count error?

Tia.

[Patrick M. Hausen]

Run

  fsck -y

in single user mode.

[hushcoden]

Thanks, so I did that way and once in signle user mode, I got this:

Code: [Select]

# fsck -y
** /dev/gpt/rootfs
** Last Mounted on /mnt
** 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
71646 files, 1018270 used, 26970326 free (5014 frags, 3370664 blocks, 0.0% frag)

***** FILE SYSTEM IS CLEAN *****
#
After restarting, I still see a few errors, is it normal?

Code: [Select]

root@hush:~ # fsck
** /dev/gpt/rootfs (NO WRITE)
** Last Mounted on /mnt
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT FILE I=2006450  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 16:44 2021  COUNT 2 SHOULD BE 1
ADJUST? no

LINK COUNT FILE I=2006476  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:00 2021  COUNT 2 SHOULD BE 1
ADJUST? no

LINK COUNT FILE I=2006506  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:11 2021  COUNT 2 SHOULD BE 1
ADJUST? no

LINK COUNT FILE I=2006509  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:33 2021  COUNT 2 SHOULD BE 1
ADJUST? no

UNREF FILE  I=2006510  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:44 2021
RECONNECT? no


CLEAR? no

UNREF FILE  I=2006524  OWNER=operator MODE=100400
SIZE=0 MTIME=Mar 20 17:44 2021
RECONNECT? no


CLEAR? no

LINK COUNT FILE I=2006565  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 16:33 2021  COUNT 2 SHOULD BE 1
ADJUST? no

LINK COUNT FILE I=2006585  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 16:55 2021  COUNT 2 SHOULD BE 1
ADJUST? no

LINK COUNT FILE I=2006595  OWNER=operator MODE=100400
SIZE=4096 MTIME=Mar 20 17:22 2021  COUNT 2 SHOULD BE 1
ADJUST? no

** 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

71667 files, 1002761 used, 26985631 free (5047 frags, 3372573 blocks, 0.0% fragmentation)
root@hush:~ #

[Patrick M. Hausen]

You never should run fsck on a live system! Your filesystem is most probably ok. Inconsistencies exist because your system is up and running ...

That's why you need to boot into single user mode. Then the filesystem is mounted read-only and fsck can work on it.

[hushcoden]

Okay, understood