Errors in fsck output on 1.2.3 release



  • I've installed pfSense 1.2.3 RELEASE on my box (had 1.2.2 running on it for a year). Logged via SSH and executed fsck. The output was strange:

    fsck

    ** /dev/ar0s1a (NO WRITE)
    ** Last Mounted on /
    ** Root file system
    ** Phase 1 - Check Blocks and Sizes
    INCORRECT BLOCK COUNT I=8714310 (4 should be 0)
    CORRECT? no

    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    UNREF FILE I=8714243  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714244  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714245  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714246  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714247  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714276  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714277  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714278  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714279  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714280  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714283  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714284  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714285  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714286  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714287  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714289  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714290  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714291  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714292  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714293  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714295  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714296  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714297  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714298  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    CLEAR? no

    UNREF FILE I=8714299  OWNER=root MODE=100644
    SIZE=0 MTIME=Jan 11 13:42 2010
    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

    20458 files, 148062 used, 36678593 free (2073 frags, 4584565 blocks, 0.0% fragmentation)

    What's with my installation? pfSense is installed on RAID1 mirror of 2 SATA HDDs



  • Why were you running fsck on a mounted filesystem?  Of course this isn't going to work!  Things are changing as it is looking at them, and it has no permission to change anything anyway.  Was there a problem that led you to want to run fsck?



  • I just wanted to ensure everything is allright
    Should I now repair partition with fsck -y in single user mode or it is normal?



  • There is no indication there is a problem.  If there was, fsck should run automatically at boot.



  • So… what do these errors mean actually?



  • On a quiescent filesystem, they might mean something.  On an active one, with things changing, they mean nothing.  If you want to know what specifically the messages might mean in a real situation, go look at some freebsd documentation.



  • Ok, I assume it's nothing to worry about


Log in to reply