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+? -- New ext3 partitions should not have max-mount count https://bugs.launchpad.net/bugs/3581 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
