[SOLVED] How to tell if e2fsck will automatically run when I restart RHEL server?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How to tell if e2fsck will automatically run when I restart RHEL server?
Is there a way to tell if e2fsck will automatically run when I restart a server? The way I understand it is if the system things a mount is dirty, it will run e2fsck on it upon reboot.
Is there a way to look in some file or something before I restart it to tell if that will happen or not?
I know on Windows servers you can look at a registry key to see if a chkdsk will run at reboot.
The filesystem will only be marked dirty if the system doesn't shut down properly. So if the system is up and running normally, and you shut it down properly, there will be no need for it to check the filesystem.
But if you do a hard power off, or the system locks, then it will not be cleanly unmounted and the check will be preformed.
fsck is used to check and optionally repair one or more Linux file systems. You don't have to create or alter/modify any file. All you need to do is just create empty file /forcefsck.
so doesn't it also set itself to run if the journaling on ext3 filesystems gets hosed? I'm just overly paranoid i'm due for a long reboot because i have a server that's been running for a long time, and I know a drive recently failed then switched over to a hot spare causing errors in the messages log.
So are you saying if I do a tune2fs -l /dev/sdXX then it will tell me if its going to run when i reboot? do you know how it specifically words it, just so I know what I'm looking for?
If the mount-count parameter is greater than max-mount-count parameter for a filesystem, the filesystem will be checked at the next reboot. Use tune2fs to see or adjust the current values for any filesystem.
An alternative method is to use the interval-between-checks parameter to specify the maximum time between filesystem checks.
running the tune2fs on one of my servers, it says the Filesystem state is "clean", but then has the following. does that mean anything special when Maximum mount count is -1.
Filesystem created: Fri Dec 29 07:15:32 2006
Last mount time: Mon Feb 2 11:58:05 2009
Last write time: Mon Feb 2 11:58:05 2009
Mount count: 18
Maximum mount count: -1
Last checked: Fri Dec 29 07:15:32 2006
Check interval: 0 (<none>)
See the manual http://linux.die.net/man/8/tune2fs
Looking at the -c, -i switches, those (your) values mean auto fsck has been disabled.
However NB:
Quote:
A filesystem error detected by the kernel will still force an fsck on the next reboot, but it may already be too late to prevent data loss at that point.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.