Le lundi 04 février 2013 à 16:23 +0100, Zbigniew Jędrzejewski-Szmek a écrit : > Hi, > > 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 <u...@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 > Description=/home/zbyszek/debian-x32/home > SourcePath=/proc/self/mountinfo > > > > 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 https://build.opensuse.org/package/view_file?expand=1&file=fix-umount-order-at-shutdown.patch&package=systemd.openSUSE_12.2_Update&project=home%3Afcrozat%3Abranches%3AopenSUSE%3A12.2%3AUpdate ) -- Frederic Crozat <fcro...@suse.com> SUSE _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel