fsck and controlling when they take place
fsck (file system consitency check) file system checks should be performed on a regular basis to fix any inconsistencies. Bt default, on RedHat Linux (and many other linux distros), fsck is triggered every 6 months on the next reboot after this point in time. However, this may not always be convenient. For example, on a recent reboot I performed, a 2TB filesystem took over an hour for the fsck to run. If you need the server back up quicker, you can choose to bypass the fsck.
To check when the next fsck is due:
tune2fs -l /dev/mapper/vg07-lvoradata6 | grep "Next check" Next check after: Tue Feb 13 12:06:09 2018
To disable fsck, you can edit /etc/fstab , changing the last character to a zero, e.g. from:
/dev/vg02/lvoradata1 /oradata1 ext3 defaults 1 2
to
/dev/vg02/lvoradata1 /oradata1 ext3 defaults 1 0
or, using the tune2fs command
tune2fs -c0 -i0 /dev/mapper/vg07-lvoradata6
Conversely, a fsck can ve forced on the next reboot as follows:
# cd / # touch forcefsck
Modern filesystems like xfs do not use fsck