Bug#758902: systemd: Please make ^C interrupt systemd-fsck

alberto fuentes pajaro at gmail.com
Tue Dec 23 20:28:46 GMT 2014


On Tue, Dec 23, 2014 at 8:02 PM, Brian Potkin <claremont102 at gmail.com> wrote:
> File systems created with mk2fs on fresh Wheezy and Jessie installs have
> mount-count and time based file checking disabled. That's quite a few
> people who are never liable to experience a surprise fsck.

My hunch tells me that there are more fs pre-wheezy than post-wheezy
out there, considering Wheezy was only released ~1.5 years ago

> Disabling perodic checking (which upstream doesn't regard as conferring
> any particular benefit) eliminates the surprise factor. Without elements
> of surprise and inconvenience to combat there is no need to overstrive
> for a solution. A fsck can always be run by a user as part of regular
> maintenance.

Well, I just learned this. It's good to know that upstream think is
safe and good to know that the default was changed as well. I wish the
defaults of my partitions had changed on the upgrade as well


> Wishlist is about right for this bug; there isn't a lower severity
> level.

hehe.

At least is mentioned once in this bug that the *recommended upgrade
path* for your ext fs includes to disable the automatic check on the
fs, and so prevent this bug from happening in the future

[...]
> The first statement is misleading; new Wheezy and Jessie users would
> disagree with it. They also realise that the consequences of enabling
> mount-count or time based file checking falls on them, not someone else.

If it is indeed misleading let me rephrase it.

The system refuses to bootup until the check is done to anybody that
has a partition formated with defaults values provided by debian
before ~1.5 years.

For example, if you are installing wheezy, but you are using a /home
partition from a previous installation, you are still affected by this
bug


IMOH, It's a really bad attitude to not take into account most of the
user base of your installations, especially in transitions like the
systemd one, where there's already plenty of bad blood

I love debian very much, and so this is nothing i can't deal with...
but I understand people which are at the edge


Cheers




More information about the Pkg-systemd-maintainers mailing list