>
> Most likely you built your LVM/dm userspace without proper udev
> support, or left support in there that creates device nodes on its
> own.
>
> Nowadays with devtmpfs device nodes are created exclusively by the
> kernel and userspace should never create a single device node. If your
> LVM/DM t
On Sun, 26.07.15 11:39, Oleksii Shevchuk (alx...@gmail.com) wrote:
> Andrei Borzenkov writes:
>
> >
> > Could you verify with e.g. inotifywatch whether inotify event was
> > generated by kernel?
> >
>
> It turns out, that for some reason I have several dm devices:
>
> # ls -l /dev/mapper/
> cr
В Mon, 27 Jul 2015 08:15:45 +0300
Oleksii Shevchuk пишет:
> Andrei Borzenkov writes:
>
> > So that it the problem. Does it happen if you use cryptsetup directly?
>
> Yes, with cryptsetup behavior is the same.
>
> I have cryptsetup (1.6.7) and lvm2 (2.02.116).
>
> Btw, does your system behave
Andrei Borzenkov writes:
> So that it the problem. Does it happen if you use cryptsetup directly?
Yes, with cryptsetup behavior is the same.
I have cryptsetup (1.6.7) and lvm2 (2.02.116).
Btw, does your system behave differently?
//wbr
//Oleksii Shevchuk
__
В Sun, 26 Jul 2015 11:39:17 +0300
Oleksii Shevchuk пишет:
> Andrei Borzenkov writes:
>
> >
> > Could you verify with e.g. inotifywatch whether inotify event was
> > generated by kernel?
> >
>
> It turns out, that for some reason I have several dm devices:
>
> # ls -l /dev/mapper/
> crw-rw
Andrei Borzenkov writes:
>
> Could you verify with e.g. inotifywatch whether inotify event was
> generated by kernel?
>
It turns out, that for some reason I have several dm devices:
# ls -l /dev/mapper/
crw-rw 1 root dialout 10, 236 ??? 25 09:52 control
brw--- 1 root root254, 12 ?
В Sat, 25 Jul 2015 09:51:25 +0300
Oleksii Shevchuk пишет:
> Hi list.
>
> I ran into the strange problem.
> After creating encrypted swap (with crypttab) boot hangs. That happens
> because systemd waits for dev-mapper-swap.device.
>
> Udev doesn't report that this device active, because SYSTEMD_
Hi list.
I ran into the strange problem.
After creating encrypted swap (with crypttab) boot hangs. That happens
because systemd waits for dev-mapper-swap.device.
Udev doesn't report that this device active, because SYSTEMD_READY
environment set to "0".
That happens because "change" event was not
