RE: Preventing ext3 fsck at boot?

Check the man page of fstab.

The last field in every record indicates whether the file system is checked on reboot.

Cheers,
Mike.

-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Sandor W. Sklar
Sent: Friday, September 28, 2007 2:42 PM
To: General Red Hat Linux discussion list
Subject: Preventing ext3 fsck at boot?

I've got a number of large EXT3 filesystems (2-8 TB each), presented
via dual-path Fibre HBAs via SAN switches from several Nexsan
SATAbeast arrays, to a number of systems running RHEL4.

The question of whether EXT3 is the right filesystem to be using for
this is probably best saved for another email (but I'd love to hear
about better options; I'm relatively new to Linux, compared to AIX
and Solaris.)

My main problem is that when we reboot these servers for scheduled
maintenance (or for any reason), odds are pretty good that I'm going
to get the (dreaded) ...

/dev/nsvg/lvol0 has gone 182 days without being checked, check forced.

... message, and then my downtime is extended by 2-3 hours while the
system does its fsck (and usually finds o problems.)

So, my questions are:

- The man page for tune2fs says that this can be disabled with the "-
c" option, but recommends strongly against it. Is it really such a
bad thing to disable, if I'm using EXT3 (with the journaling that
makes it "3" instead of "2")? I've used JFS/JFS2 for years on AIX,
and UFS journaling on Solaris, and neither seems to want to force an
fsck just because some arbitrary time period has past since it last
checked.


- If the consensus is that it would be ok to disable these checks,
what is the proper syntax? I tried:

# tune2fs -c0 /dev/mapper/nsvg-lvol0
tune2fs 1.35 (28-Feb-2004)
Setting maximal mount count to -1

... but that didn't work. Looking for some practical advice and
recommendations, here, please!

Thanks,
-s-

--
Sandor W. Sklar
Unix Systems Administrator
Stanford University Libraries & Academic Information Resources (SULAIR)
Digital Libraries Systems & Services (DLSS)


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Relevant Pages

  • Re: [PATCH] Clustering indirect blocks in Ext3
    ... This patch modifies the block allocation strategy in ext3 in order to ... Slow fsck is not a serious problem on ... Most of Ext3 metadata is clustered on disk. ... indirect blocks are an exception. ...
    (Linux-Kernel)
  • Re: Ubuntu has corrupted my file !
    ... This morning Ubuntu's boot make a fsck (check forced, ... Ext3 would still use the same settings - so you need to change the fsck ... and reformat with filesystem that supports journalling. ... The ancient filesystem is pretty reliable - that's why it's still around. ...
    (Ubuntu)
  • Re: [Lug-nuts] fsck: Unexpected Inconsistency
    ... > We had a power outage a few days ago, and my linux machine went down. ... Run fsck on the affected partition, without using the -a or -p options. ... filesystem to ext3; just umount the partition and do "tune2fs -j" on it. ...
    (comp.os.linux.misc)
  • Re: avoiding but satisfying disk check on startup
    ... I've changed it to ext3. ... There are 3 reasons for the system to run an automatic fsck ... The file system is flagged as dirty. ... journaling filing system) to schedule time for explicit fscks. ...
    (comp.os.linux.hardware)
  • Re: [CALL FOR TESTING] Make Ext3 fsck way faster [2.6.24-rc6 -mm patch]
    ... people will fsck their ext3 filesystems during ... planned downtime, and the benefit of reducing that downtime from 6 ... They won't fsck in planned downtimes. ...
    (Linux-Kernel)