Hello, there. If you run fsck on a mounted filesystem, fsck will not do anything, except if you ask it to run without correcting anything — in fact, if my memory serves me well, even a read-only check will likely fail because of the filesystem changes made by processes as fsck works on it. The only way to let him correct errors found and update filesystem check counters is to unmount the filesystem before checking it; this implies shutting down any service or task using it before starting fsck, so, if your goal in to minimize shutdown delay, it won't really work. Besides, you just can't do this with your / filesystem, so it can only be checked on startup. As you can see, it would be much easier and effective to schedule a full system fsck at next reboot and schedule this reboot at a low load moment.
Regards. P.-S.: hoping I'm not saying bullshit; as a sysadmin, I use fsck only during reboots as much as I can. Le vendredi 26 septembre 2014 à 17:51 +0500, Muhammad Yousuf Khan a écrit : > hello all, > > > i have several debian server and they are up 24/7. even i have a > server which is up for 1.5 years. without restart. > > > now i know when ever i restart this for the maintenance it will run > the fsck to check the disk. which is fine and i have heard that it is > very important to run on boot but what i want to know if fsck process > is that critical do i need to run fsck manually. so that i can save my > server from restart just for fsck. > or i can cron job the task once every moth or two is this a good > idea. > > > Thanks, > MYK -- David Guyot Administrateur système, réseau et télécom / Sysadmin Europe Camions Interactive / Stockway Moulin Collot F-88500 Ambacourt 03 29 30 47 85
signature.asc
Description: This is a digitally signed message part
