Re: Skipping fsck during boot with systemd?
On Sat 06 Dec 2014 at 10:10:05 +0000, Lisi Reisz wrote:
> On Saturday 06 December 2014 09:44:38 Brian wrote:
> > On Sat 06 Dec 2014 at 06:42:50 +0000, Lisi Reisz wrote:
> > > On Friday 05 December 2014 23:16:47 Brian wrote:
> > > > On Fri 05 Dec 2014 at 19:06:50 -0300, Renaud OLGIATI wrote:
> > > > > On Fri, 5 Dec 2014 20:59:25 +0000
> > > > >
> > > > > Brian <ad44@cityscape.co.uk> wrote:
> > > > > > But remember our current slogan "Linux is all about choice". One
> > > > > > can choose to boot with or without "fsck.mode=skip".
> > > > >
> > > > > What about the choice to stop fsck it if it has started at an
> > > > > inconvenient moment ?
> > > >
> > > > Remedial action is not needed because the right choice was made from
> > > > the grub menu. If it wasn't, you get to live with the consequences and
> > > > don't do it again.
> > >
> > > Eduardo was late! Haven't you ever been late for anything and wanted to
> > > speed something up??
> >
> > His lateness and the scheduled fsck do not appear to be correlated. A
> > technique to speed things up has been given.
>
> But his lateness and his desire to interrupt the fsck on that particular
> occasion are directly causally linked. To say "Your mistake. You should
> have done so and so. You must live with the consequences if you didn't." is
> neither very pleasant nor very helpful. As I say, most of us are human and
> make mistakes sometimes.
>
> Eduardo probably usually wants fsck to run. Just not on that occasion. So
> your "solution" didn't even solve the problem.
>
> Lisi
>
> > > Most of us are human and make occasional mistakes.
> >
> > It is evident from this thread that the ability to abort an in-progress
> > fsck during boot may not be available yet (although the links given
> > indicate some untested possibilities). Another suggestion would be to
> > have a system detect an impending fsck and have it substitute a grub.cfg
> > with "fsck.mode=skip" in it for the next boot.
In what way does having two grub entries not answer the need to have
fsck run most of the time but not run on occasions which are deemed
inconvenient?
A third suggestion is to use grub's scripting to present the user with
a choice of a fsck or not.
Reply to: