INCORRECT BLOCK COUNT and UNALLOCATED errors

[Woodchuck]

On Thu, 2 Nov 2006, Lou Hevly wrote:

> Greetings:
> 
> I'm getting INCORRECT BLOCK COUNT and UNALLOCATED  errors when fscking 
> two of my partitions (/var and /home; output and dmesg attached below).
> 
> Can I run fsck interactively by doing the following?
> 
> umount /var
> fsck -p /dev/wd0e
> (of perhaps fsck -p /dev/wd0e)
> mount /dev/wd0e /var

Why the -p (preen) option?

The system need not be single-user to run fsck.

However,  you will need to isolate the system and perhaps kill various
processes. (Those with files open on /var or whatever filesystem you
are fsck'ing).   Do not be umounting /var or /home on a system with
random users and processes.  You want a quiet system.

Man 8 init, see the bit about kill -s TSTP 1, I've never tried that.

> This is a remote machine and I'd have to pay someone to boot it into 
> single user mode.
> 
> 
> $ fsck /dev/wd0e
> ** /dev/rwd0e (NO WRITE)
> ** Last Mounted on /var
> ** Phase 1 - Check Blocks and Sizes
> INCORRECT BLOCK COUNT I=186033 (8 should be 0)
> CORRECT? no

Here's a question... why not say "yes"?  (or is this "preen" output?
I've never used -p).

Also, just rebooting will (usually) clear these errors.

Or are you somehow bypassing the fsck at boot?

Dave