[systemd-devel] Second (erroneous) check of rootfs?

Nikolai Zhubr n-a-zhubr at yandex.ru
Sat Jan 10 05:51:24 PST 2015

09.01.2015 23:48, Chris Murphy:
>> I might be missing something, but what's wrong with the existing "root=...
>> rootfstype=... rootflags=... rw" options? Why is the remount even necessary?
> Seems to be distro specific. I see rw for opensuse or Ubuntu, and ro for Fedora.
> The ro seems antiquated to me, meant for interactive fsck on an ro
> mounted filesystem when booting single user. 'btrfs check' refuses to
> run on mounted file systems, even if ro. And xfs_repair requires the
> use of -d "repair dangerously" to do so.
> Both XFS and Btrfs have placeholder fsck's, if you man fsck.xfs or
> fsck.btrfs you'll see. These filesystems are designed to fix most

Ok. I've invented a quick-and-dirty fix. I'll modify systemd-fsck so 
that when run with no argument it does nothing and exit successfully. 
This way I'll still have rootfs fsck'ed every boot, but never twice.

I'll soon need this box for work anyway, reverting to some 12.x does not 
seem very attractive, and living with this bug every day won't give me a 
good feeling either. (Just a week ago I had one single erroneous fsck 
rendering my rootfs essentially to a complete trash)

Hope someone will come up with a better solution though :)
(There are lots of systems affected to some degree in the wild already)

Thank you,

More information about the systemd-devel mailing list