[systemd-devel] [PATCH 1/2] core: keep mountinfo .mounts until late shutdown
fcrozat at suse.com
Mon Feb 4 07:46:21 PST 2013
Le lundi 04 février 2013 à 16:23 +0100, Zbigniew Jędrzejewski-Szmek a
> On Mon, Feb 04, 2013 at 03:03:59PM +0100, Umut Tezduyar wrote:
> > Downside of this patch is, mountinfo mounts stick around as inactive-dead
> > even when the file system they represent is unmounted.
> > On Mon, Feb 4, 2013 at 3:00 PM, Umut Tezduyar <umut at tezduyar.com> wrote:
> > > .mount units coming from /proc/self/mountinfo file are
> > > unmounted after local-fs.target is reached during shutdown.
> > >
> > > Problem: .mount units popping up in mountinfo file are
> > > added to systemd without any dependency. For that reason,
> Hm, what do you mean exactly by that? Mount units I see have dependencies
> on mount points higher in the hierarchy. E.g.
> Requires=systemd-journald.socket -.mount home.mount
> After=systemd-journald.socket -.mount home.mount
> > > they are the first one to be unmounted during shutdown.
> This seems correct. Usually they were mounted last, by an admin,
> and should be unmounted first.
There was a bug in v44 where some mount points mounted by initscripts
(for instance /var/lib/nfs/rpc_pipefs in nfs initscript) which was
unmounted before initscripts were stopped but it was fixed during the
rewrite done for fstab-generator (I've extracted it as
Frederic Crozat <fcrozat at suse.com>
More information about the systemd-devel