[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Skipping fsck during boot with systemd?

On 12/11/2014 1:23 PM, Brian wrote:
> On Thu 11 Dec 2014 at 12:11:26 -0500, Jerry Stuckle wrote:
>> If Windows can give you the option as to when to perform a potentially
>> critical (do not shut down!) and long running process, why can't Linux?
> As far as having the option of an fsck at boot is concerned I've already
> mentioned grub's datehook module. Ok, you have to set it up in grub.cfg
> but then you can forget about ever having an fsck run at an inconvenient
> time. Assuming your presentations tend to take place between 10:00 and
> 20:00 the machine would be configured to not run an fsck during that
> time slot.

OK, so I set it up not to run between 07:30 and 21:00 (some
presentations start as early as 8:00 AM and some evening presentations
as late as 8:30 PM).  This means fsck will never run because I don't use
the laptop outside of those times.

>> Or, better yet, give the option to cancel it if it does start at the
>> wrong time.
> For less work to set up than the previous method you want to take a look
> at
>    https://bugzilla.redhat.com/show_bug.cgi?id=799574

To which Lennart responded that is not a good idea.

>> I often give presentations with my notebook.  If I'm lucky, I get 10-15
>> minutes to set up.  If I'm not, less than 5 minutes (i.e. another
>> presenter ahead of me).  I use Linux whenever possible, but since my
>> time slot is limited, I can't wait for fsck to complete.
> Your type of situation is well understood and there is sympathy for it.

I appreciate that - but unfortunately, sympathy doesn't solve the problem :)


Reply to: