On Wed, Jul 02, 2014 at 12:33:01PM -0600, Chris Murphy wrote: > > On Jul 2, 2014, at 5:39 AM, Daniel Drake <dr...@endlessm.com> wrote: > > > Hi, > > > > I'm trying to understand dracut/systemd fsck behaviour, in the context > > of an ext4 filesystem root mounted read-only from dracut, remaining > > read-only even when the system is fully booted (kiosk-style). > > > > I see that systemd's fstab-generator rightly creates a mount unit for > > /sysroot from the initramfs, and causes e2fsck to be run on it from > > inside the dracut initramfs, before it is mounted. So far so good. > > It's not wrong, but it seems unnecessary to fsck an ro file system. How is it > becoming inconsistent if it's read only? >
You still need to remount / rw for administration tasks or updates.
Cheers,
--
Leonid Isaev
GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4
C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
pgpyyl9U8mlO8.pgp
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
