Ext3 users - Mar 2010 - fstab Pass Column and forced disk checks

If I have the 6th column in fstab (the pass column) set to 0, does that mean
disk checks will never be forced at boot regardless of anything like File
System State, Mount Count, and Check Interval on the file system itself, or
are there exceptions to this?

I know `man fstab` says:
If the sixth field is not present or zero, a value of zero is returned and
fsck will assume that the filesystem does not need to be checked.

But I wasn't sure if the fsck might be triggered in other ways during boot.

Thank you,
Kyle Brandt
http://www.kbrandt.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/ext3-users/attachments/20100309/d1a49630/attachment.htm>

If the pass column is 0, no automatic check is done.
It's been my experience that setting it that way is a bad idea though,
unless you plan on periodic manual fscks.

----- "Kyle Brandt" <kyle at kbrandt.com> wrote:
> If I have the 6th column in fstab (the pass column) set to 0, does
> that mean disk checks will never be forced at boot regardless of
> anything like File System State, Mount Count, and Check Interval on
> the file system itself, or are there exceptions to this?
> 
> I know `man fstab` says:
> If the sixth field is not present or zero, a value of zero is returned
> and fsck will assume that the filesystem does not need to be checked.
> 
> But I wasn't sure if the fsck might be triggered in other ways during
> boot.
> 
> Thank you,
> Kyle Brandt
> http://www.kbrandt.com
> 
> _______________________________________________
> Ext3-users mailing list
> Ext3-users at redhat.com
> https://www.redhat.com/mailman/listinfo/ext3-users

On 2010-03-09, at 10:10, Kyle Brandt wrote:
> If I have the 6th column in fstab (the pass column) set to 0, does  
> that mean disk checks will never be forced at boot regardless of  
> anything like File System State, Mount Count, and Check Interval on  
> the file system itself, or are there exceptions to this?
No, there are many filesystems which don't have/allow checking so the  
top-level fsck tool needs to honor this.  I would never recommend  
disabling e2fsck on a system, unless you are running in an HA  
environment where it is not safe to do automated checks at startup  
time.  I also do not recommend that people disable the periodic e2fsck  
checks, because people forget to check their filesystems, and the  
kernel can sometimes spread corruption further if it reads garbage  
from the disk.

If you dislike the periodic (time/mount count) checks that e2fsck  
forces at boot, I would suggest using the "lvcheck" script I posted to
linux-ext4 some months ago (assuming you are using LVM, which most  
people are these days), and will attach here again. That allows you to  
periodically check the filesystem in the background to detect  
corruptions on disk, without any concern that the next reboot will  
take a long time.

It would be great to get these included as part of the lvm2 package,  
and have lvcheck installed in /etc/cron.weekly to automatically check  
all the LVs configured on the system, and solve the "we don't like  
periodic checks at boot" problem in a way that is still robust to the  
errors that will undoubtably appear on disk at one point or another.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvcheck
Type: application/octet-stream
Size: 10785 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ext3-users/attachments/20100309/38db7958/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvcheck.conf
Type: application/octet-stream
Size: 1242 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ext3-users/attachments/20100309/38db7958/attachment-0001.obj>