Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 03 Jan 1999 15:23:09 -0500
From:      Graeme Tait <graeme@echidna.com>
To:        freebsd-questions@FreeBSD.ORG
Cc:        Graeme@echidna.com
Subject:   fsck -n finds errors in operating server
Message-ID:  <368FD1AD.4B@echidna.com>

next in thread | raw e-mail | index | archive | help
I have a FreeBSD/Apache web server which has been running fine for 
almost 50 days since the last reboot.

I just ran fsck -n out of curiousity, and got in part the following:


** /dev/rda0s1e (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
** Phase 5 - Check Cyl groups
BLK(S) MISSING IN BIT MAPS
SALVAGE? no

SUMMARY INFORMATION BAD
SALVAGE? no

CLEAN FLAG NOT SET IN SUPERBLOCK
FIX? no

11830 files, 915788 used, 574323 free (12715 frags, 70201 blocks, 0.9% 
fragmentation)


Apart from a few a few user tasks having crashed or been killed, I'm not 
aware of any problems on this machine.

So my first question is, how does filesystem damage (I assume the above 
problems are minor and repairable) occur in this situation? Shouldn't 
the kernel isolate the filesystem integrity from application problems?

Secondly, can these problems be repaired without taking the server down? 
Is it worth repairing them? (At least if the system were clean, it would 
be clear if further problems occurred.)


-- 
Graeme Tait - Echidna


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?368FD1AD.4B>