It may have been checked due to "Max mount counts" or "Interval
between
checks" bits set in the filesystem itself. What version of e2fs utils are
you using in this case?
You can do 'dumpe2fs -h <rootfs_device> | less' and note the max
mount
count and check interval fields. No matter what, checks will be performed
via fsck if either of these fields reaches a valid state, ie. it's been
more than a month since last fsck, etc.
These two fields can be altered via the tune2fs command.
Hope that helps clear things up for you. :)
On Mon, 29 Jan 2001, Douglas J. Hunley wrote:
> Date: Mon, 29 Jan 2001 10:19:38 -0500
> From: Douglas J. Hunley <root@hunley.homeip.net>
> Reply-To: ext3-users@redhat.com
> To: ext3 <ext3-users@redhat.com>
> Subject: weirdness on powerfail
>
> I had a power-fail this morning, and when I rebooted, /etc/rc.d/rc.boot
> issued a 'mount -n -o remount,ro /' and then a 'fsck -A -V -a
-C'. The
> fsck failed on my root partition. I know why it failed. It called
> fsck.ext2 . My root poartition is ext3. My question is, why did it call
> fsck.ext2? Another question, why was it checked at all? My /etc/fstab
> contains:
> /dev/hda1 / ext3 defaults,check=none 0 0
>
> What's going on here?
> --
> Douglas J. Hunley (Linux User #174778)
> http://hunley.homeip.net/ http://hunley.epinions.com/
> http://www.thesatorieffect.com/
>
> "This may seem a bit weird, but that's okay, because it is
weird."
>
>
>
> _______________________________________________
> Ext3-users mailing list
> Ext3-users@redhat.com
> https://listman.redhat.com/mailman/listinfo/ext3-users
>