[PLUG] Forced fsck

Elliott Mitchell ehem at m5p.com
Sun May 21 23:00:16 UTC 2006


>From: Bruce Kilpatrick <bakilpatrick at verizon.net>
> I have been watching this thread and wondering why I hadn't seen this
> forced fsck happen.  It finally occured to me...I rarely shut my Ubuntu
> box off.  It hasn't seen 30 boots since I installed Ubuntu on it.
> Judging by what I am reading here, maybe I should manually cause the
> system to run fsck once in a while???

If you keep it running long enough, you'll go into the 180 days forced
fsck. With the automatic checks in place, no need.


>From: m0gely <m0gely at telestream.com>
> I've been watching this too and am puzzled.  What's the point at all? 
> If the system is being shutdown properly then fsck shouldn't be needed 
> on boot outside of special scenarios.  BSD doesn't do this.

Even with hard shutdowns it shouldn't be needed, as the journal will
contain everything needed to restore the filesystem to a consistant
state.

This though assumes your hardware works perfectly and the filesystem code
doesn't have any sort of bugs. Alas it is rare for either of these to be
true, so the forced checks are an attempt to compensate for hardware and
software that aren't perfect. Even with ECC memory you have to watch out
for bit-rot on the filesystem.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         EHeM at gremlin.m5p.com PGP 8881EF59         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
    \___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/





More information about the PLUG mailing list