<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Please add "-f" to shutdown to skip fsck on demand"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88330#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Please add "-f" to shutdown to skip fsck on demand"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88330">bug 88330</a>
from <span class="vcard"><a class="email" href="mailto:cb@lathspell.de" title="cb@lathspell.de">cb@lathspell.de</a>
</span></b>
<pre>The requested option was primarily the "-f" aka --skip-fsck to avoid a "ten
minutes long" downtime. This option is of course only used if there is *no*
suspicion regarding the filesystem but just the fear of a lengthy fsck run at
the wrong time.
The "-F" aka "--force-fsck" is mostly used not because of a specific suspicion
but because there is a scheduled downtime anyways and the admin thinks that it
can't hurt even if only e.g. 100 of the configured 180 days are passed. After
all, it gives him 80 days in which a reboot would not to the lengthy fsck by
default.
So both options seem to have their valid use cases and can't really be called
"dangerous" per se.
It's nice that the "/forcefsck" still works, is there a "/skipfsck" as well?
It is not mentioned in fsck(8) or shutdown(8).
If so, it would be nice if this trick could at least be added to shutdown(8) as
many admins whose distros switch to systemd will soon be wondering where -f is
gone.
I'm still in favour of adding the complete -f/-F options to shutdown again.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>