[systemd-devel] fsckd needs to go

[Lennart Poettering]

On Wed, 08.04.15 13:03, Reindl Harald (h.reindl at thelounge.net) wrote:

> >>https://bugzilla.redhat.com/show_bug.cgi?id=1105877
> >
> >Hmm? i don't understand what that bug is about? Is it about /forcefsck
> >being ignored?
> 
> it is about "warning: checktime reached, running e2fsck is recommended" but
> the check didn't happen and that you *need* to "touch /forcefsck" while it
> should happen automatically

OK, reassigned to the kernel. it's somewhere between the kernel ane
e2fsck to figure this out. We will always call fsck, it's up to fsck
to do something, and if it decides not to, then it would needs to say
why, and get the kernel in sync...

> >And what does this bug have to do with systemd?
> 
> i don't get your reasoning for "Maybe the right fix for Ubuntu is to stop
> enabling the "routine" check logic?" because as seen a few months ago this
> routine check is important, otherwise you may not notice existing corruption
> (for whatever reason) until it is too late

Well, the file system folks at RH decided this makes no sense long
ago, please bring this up with them. Also note that the change RH was
carrying a long time is now upstream (see Martin's link), hence bring
this up with them.

systemd is not involved in this.

Lennart

-- 
Lennart Poettering, Red Hat