9 Nov
2012
9 Nov
'12
2:38 a.m.
Lindsay Sprinter <zlinw@mcmedia.com.au> writes:
During the twenty years I have never seen one of these "scheduled" fsck's produce any errors caused by a failure in the drive or the file system. Errors have been produced a small number of times but they have been caused by externel influences [...] So in the end one could probably turn it off as has already been suggested and lose no sleep over it.
IIRC I've seen it due to dying HDDs, so I would add an erratum that if you turn off periodic fscks of ext, make sure to turn on periodic SMART checks.
Even if you leave periodic fscks on, still do SMART checks. The two solve fairly different problems. James