Comment 24 for bug 3581

Revision history for this message
Jonathan Musther (musther-deactivatedaccount) wrote :

Using the -n switch, fsck can check a mounted filesystem (-n tells it not to make any changes, so it wont do any repairs). So the quick way to implement this would be to have a scheduled 'fsck -n', if it comes back clean, fine, if it comes back dirty, schedule a full check to run (on shutdown, with a note in the logout/shutdown dialogue?).

That should be quicker and easier to implement than writing the errors to a log for quick fixing.

Mark, are you wanting this for Hardy, or Hardy+?