Stories
Slash Boxes
Comments

SoylentNews is people

Systemd Prevents the Skipping of fsck while Booting

posted by LaminatorX on Sunday December 21 2014, @02:05AM   Printer-friendly
from the fsking-pid0 dept.

An Anonymous Coward writes:

A Debian user has recently discovered that systemd prevents the skipping of fsck while booting:

With init, skipping a scheduled fsck during boot was easy, you just pressed Ctrl+c, it was obvious! Today I was late for an online conference. I got home, turned on my computer, and systemd decided it was time to run fsck on my 1TB hard drive. Ok, I just skip it, right? Well, Ctrl+c does not work, ESC does not work, nothing seems to work. I Googled for an answer on my phone but nothing. So, is there a mysterious set of commands they came up with to skip an fsck or is it yet another flaw?

One user chimed in with a hack to work around the flaw, but it involved specifying an argument on the kernel command line. Another user described this so-called "fix" as being "Pretty damn inconvenient and un-discoverable", while yet another pointed out that the "fix" merely prevents "systemd from running fsck in the first place", and it "does not let you cancel a systemd-initiated boot-time fsck which is already in progress."

Further investigation showed that this is a known bug with systemd that was first reported in mid-2011, and remains unfixed as of late December 2014. At least one other user has also fallen victim to this bug.

How could a severe bug of this nature even happen in the first place? How can it remain unfixed over three years after it was first reported?

 
This discussion has been archived. No new comments can be posted.
Systemd Prevents the Skipping of fsck while Booting | Log In/Create an Account | Top | 129 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 1) by neleai on Sunday December 21 2014, @09:28AM

    by neleai (4923) on Sunday December 21 2014, @09:28AM (#127974)

    Why should my default behavior be to split my disk into multiple data partitions, and how is using a single partition for data a disaster waiting to happen? Disks typically fail for mechanical reasons; partitioning will not save you there. I consider it best practice to have a single root partition and a single swap partition, unless I have good reasons to do otherwise. Needlessly splitting of /usr or /home is just setting yourself up for pain when you discover you need more space for /home and less space for /usr than you expected, or vice versa. If you're using NFS or something then yeah by all means slice up your FS, but otherwise ... what's the point?

    It is also used when you have different distros then you use separate / and common /home partions.