On 12/07/2014 at 06:37 PM, Mart van de Wege wrote:
Look, if you reboot a laptop instead of suspending/hibernating it, sooner or later you're going to have to think "Hmm, it hasn't fscked for a while". It shouldn't be a surprise when it does.
That brings up a whole different question about whether the better option would be fsck after X number of
days instead of X number of boots. On 12/7/2014 5:29 PM, The Wanderer wrote:
If the option to cancel is there, then the resulting failure to do a complete fsck should mean that fsck get run again on the next boot. So there should be no foot shooting unless the choice is consciously made to cancelOf course not. But you may not be expecting it to happen *this* time - just that it will happen at some point. And you should still be able to cancel / abort it when it does happen, and just have it happen again next time - just in case that's the best option for the circumstances at hand. If that results in you shooting yourself in the foot over the long term, then that's your problem, because you made the decision to prioritize the immediate benefit of cancelling the fsck over the long-term benefit of letting it run.
the fsck on every following boot. Later, Seeker