regular fsck possible solution

[Nigel Harwood]

I asked a little while back about people's opinions regarding doing
a regular fsck on systems to prevent file system corruption going
unnoticed.

I have decided to run a script using cron on the systems in question
once a day.  The script would run fsck -n and check its output.
If no problems were found it would continue on.  If problems were found
it would then wait 10 minutes and run fsck -n again.  If none of
the problems are duplicated exactly on the second run then it will
continue on.  If they are however it will consider corruption to have
occurred and I can arrange for a proper fsck to be done in single user.

Hopefully by running fsck twice I will be able to differentiate between
valid file systems changes due to the running system and real corruption.

Thoughts ?
-- 
<<<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia     >>
<< Phone: +61 3 829 6090  E-mail: nigel at cnw01.storesys.coles.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>