systemd and mounting filesystems
mzerqung at 0pointer.de
Tue Oct 4 22:28:57 UTC 2011
On Wed, 05.10.11 00:18, Lennart Poettering (mzerqung at 0pointer.de) wrote:
> On Tue, 04.10.11 15:02, Tom Hughes (tom at compton.nu) wrote:
> > On 04/10/11 14:54, Paul Howarth wrote:
> > > I ran into a similar problem last month. I foolishly set up a bind mount
> > > for a local filesystem, with the new mountpoint living on top of an NFS
> > > filesystem, and set it up in fstab to mount on boot in an F-16 VM. When
> > > I next rebooted, the attempted bind mount happened very early in the
> > > boot process (long before the network was up) and failed, resulting in a
> > > boot failure at an even earlier point that the usual single-user mode,
> > > where all the volume groups hadn't even been scanned and devices added
> > > in /dev, which was tricky to fix until I figured out what had happened
> > > and removed the bind mount entry from fstab.
> > I have a similar problem with some bind mounts over the root filesystem
> > where systemd mounts them while the rootfs is still ro and hence they
> > all wind up as ro until I remount them.
> Is there a bugzilla about this?
> This is an interesting issue to think about. I wonder what the right fix
> should be though: delay all bind mounts after the / remount?
Hmm, if you change /etc/fstab and explicitly specify "rw" as option of
the bind mount, does that fix the issue?
Lennart Poettering - Red Hat, Inc.
More information about the devel