[systemd-devel] dev-root.device is not active, results in an umount spree

Martin Pitt martin.pitt at ubuntu.com
Mon May 18 06:51:47 PDT 2015


Lennart Poettering [2015-05-18 14:10 +0200]:
> The whole point of the "tentative" state is that devices showing up in
> /proc/self/mountinfo but not in /sys are put in it. Are you saying
> that does not work?

Simple demonstration with some bind mount:

  # systemd-nspawn -b -D /tmp/myroot --bind /etc/cron.daily/

with current systemd you'll get

  dev-sda3.device loaded inactive dead dev-sda3.device

and with the v2 patch you get

  dev-sda3.device loaded activating tentative dev-sda3.device

which is what's intended, right? (This simple setup doesn't reproduce
the overzealous unmounting yet, but it shows the wrong state)

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


More information about the systemd-devel mailing list