Johannes Wiedersich:
>
> The debian default of my sarge installations is that the ext3-FS are
> fsck'ed about every 30 mounts or 180 days (whatever comes first).
Just in case you don't know already: you can change that with tune2fs.
> What is a reasonable schedule for a server or a workstation?
I do not know of any generally applicable rule of thumb for this
question. I do not run really important production servers, but I have
switched automatic fscking off completely on most of the workstations I
am regularly using, because it can be really annoying. And after five
years of using linux I am still waiting for the day that a run of fsck
reports problems I did not know about beforehand.
To prevent unexpected data loss, I install smartmontools on my machines
and let it regularly run hardware self tests. Of course this protection
mechanism works on a lower level than checking the integrity of the file
systems, but I have never seen an ext3 or XFS filesystem being corrupt
without hardware errors (or hard shutdowns).
Production servers are different, obviously, but since you normally
don't reboot them at regular intervals, running fsck at reboot time
every $x days or every $y reboots doesn't gain you anything. I am
inclined to believe that this feature stems from earlier times when the
filesystem modules have not been as reliable as they are today.
J.
--
Whenever I hear the word 'art' I reach for my visa card.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>
Attachment:
signature.asc
Description: Digital signature