[PLUG] FSCK what's going on?

[William A Morita]

Elliott

Is there an easy way (and safe way) to set the dirty flag? 

- Bill 
wamorita at hevanet.com 


-----Original Message-----
From: plug-bounces at lists.pdxlinux.org
[mailto:plug-bounces at lists.pdxlinux.org] On Behalf Of Elliott Mitchell
Sent: Sunday, March 20, 2005 1:50 PM
To: plug at lists.pdxlinux.org
Subject: Re: [PLUG] FSCK what's going on?

>From: Carlos Konstanski <ckonstan at lunarlogic.com>  What do you mean 
>when you say "ran a fsck from knoppix"?  Did you run an  "e2fsck" 
>without the -f option, or did you run an actual "fsck"?  You  say the 
>checked out clean.  Was this right away when running the fsck  command, 
>or after a lengthy disk check?  e2fsck without a -f will often  not 
>even bother to run a disk check.

(Because it checks the clean flag on the filesystem, and unless there is a
panic or other unclean shutdown that does tend to get reset.)

> e2fsck is a wrapper around fsck.ext3.  I'm thinking it's kinda 
> pointless to run e2fsck.  Maybe use fsck directly instead.

Other way around. `fsck` is a pretty simple wrapper for `fsck.<fs>` (where
<fs> is "ext2", "ext3" or whatever). `fsck.ext2` and `fsck.ext3` are
generally symbolic links to `e2fsck`. The fun part is unless the FS is
actively marked as dirty (kernel checks found inconsistancies) or it has
exceeded the mount count, `fsck.ext3` is a no-op as it lets the kernel do
journal playback.


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


_______________________________________________
PLUG mailing list
PLUG at lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug