<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: introduce a way to request/skip fsck on next reboot" href="https://bugs.freedesktop.org/show_bug.cgi?id=88330#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: introduce a way to request/skip fsck on next reboot" href="https://bugs.freedesktop.org/show_bug.cgi?id=88330">bug 88330</a> from <a class="email" href="mailto:kay@vrfy.org" title="Kay Sievers <kay@vrfy.org>"> Kay Sievers</a> <pre>(In reply to cb from <a href="show_bug.cgi?id=88330#c7">comment #7</a>) > @Kai: what is the problem with forcing/skipping the fsck by creating a dummy > file in the root file system like Linux did it for years? The filesystem is > writable before the reboot when the /forcefsck is created, readable when > fsck is called before mounting it and writable again after mounting so that > the dummy file can be removed by some init script. Requiring to write to the content of a filesystem that one suspects to need a fsck is nothing but a really bad idea. <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: introduce a way to request/skip fsck on next reboot" href="show_bug.cgi?id=88330#c1">https://bugs.freedesktop.org/show_bug.cgi?id=88330#c1</a> If legacy filesystems need that fiddling, then they have to provide the facilities to make that happen. It is not the job of the "init system" to invent insufficient and conceptually broken work-arounds for missing features in these legacy tools. <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: introduce a way to request/skip fsck on next reboot" href="show_bug.cgi?id=88330#c6">https://bugs.freedesktop.org/show_bug.cgi?id=88330#c6</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>