[systemd-devel] initrd mount inactive

[Lennart Poettering]

On Thu, 30.04.15 15:20, Aaron_Wright at selinc.com (Aaron_Wright at selinc.com) wrote:

> Lennart Poettering <lennart at poettering.net> wrote on 04/30/2015 02:39:45 
> AM:
> > On Wed, 29.04.15 12:09, Aaron_Wright at selinc.com 
> > (Aaron_Wright at selinc.com) wrote:
> > 
> > > I applied those other commits you listed, and I took a look at the 
> lvm2 
> > > package, which was being compile with "--disable-udev_sync" and "
> > > --disable-udev_rules". I enabled both of those and recompiled both 
> lvm2 
> > > and systemd.
> > > 
> > > Nothing changed. Sometimes var.mount is still bound to an inactive 
> > > /dev/mapper/<name>.
> > 
> > Well, it will be bound to it, but systemd should not act on it
> > anymore and unmount it.
> > 
> > Also, th device should become active as soon as udev ran and 
> > reprobed everything.
> > 
> > > Do I need the *.rules files from lvm2?
> > 
> > Well, you do need the DM ones at least. That's actually where the
> > interesting bits are sicne they properly probe the LUKS device and
> > make it available for other components including systemd to pick it up.
> 
> I added a couple udev rules that are present in the Ubuntu dmsetup package 
> for my distribution, and now I get a couple errors from systemd-udevd:
> 
> systemd-udevd[153]: conflicting device node 
> '/dev/mapper/91caea2d-0e19-441e-9ea7-7be1ed345e96' found, link to 
> '/dev/dm-1' will not be created
> systemd-udevd[154]: conflicting device node 
> '/dev/mapper/d8668b2e-3a40-46df-8c64-f369a1a7a09c' found, link to 
> '/dev/dm-0' will not be created
>
> With status as:
> 
>   dev-mapper-91caea2d\x2d0e19\x2d441e\x2d9ea7\x2d7be1ed345e96.device 
> loaded    activating tentative 
> /dev/mapper/91caea2d-0e19-441e-9ea7-7be1ed345e96
>   dev-mapper-d8668b2e\x2d3a40\x2d46df\x2d8c64\x2df369a1a7a09c.device 
> loaded    activating tentative 
> /dev/mapper/d8668b2e-3a40-46df-8c64-f369a1a7a09c
> 
> The system seems to work just fine though, so I'm wondering if I should 
> ignore these errors and move on. I'm sure what the impact is.

If they stay tentative then this isn't working correctly. After udev
is up and probed the devcies they should really be set to "plugged"
and not "tentative" anymore. There's something still wrong with your
udev rules I fear...

Lennart

-- 
Lennart Poettering, Red Hat