Bug#402511: #402511 lvm-common: bogus errors during shutdown when using encrypted partition on LV

Frans Pop elendil at planet.nl
Wed Jan 10 14:02:24 CET 2007


retitle 402511 Device nodes are not removed when devices are brought down
clone 402511 -1
reassign -1 cryptsetup
thanks

I'm cloning this BR to cryptsetup as the problem seems to be not that
the lvm init script loops over the device nodes, but that the device nodes
are not removed when the corresponding crypto devices are brought down.

I'd expect that device nodes that are created dynamically when a lvm or
crypto device is created, would also be removed dynamically when the
corresponding device is brought down.

I am cloning the BR as lvm-common has the same problem for devices
corresponding to LVs that are brought down.

On shutdown, before /etc/rc0.d/S48cryptdisks is run I have:
brw-rw---- 1 root disk 254,  0 2007-01-10 12:51 /dev/dm-0
brw-rw---- 1 root disk 254,  1 2007-01-10 12:51 /dev/dm-1
brw-rw---- 1 root disk 254,  2 2007-01-10 12:51 /dev/dm-2
brw-rw---- 1 root disk 254,  3 2007-01-10 12:51 /dev/dm-3
brw-rw---- 1 root disk 254,  4 2007-01-10 12:51 /dev/dm-4
brw-rw---- 1 root disk 254,  5 2007-01-10 12:51 /dev/dm-5
brw-rw---- 1 root disk 254,  6 2007-01-10 12:52 /dev/dm-6
brw-rw---- 1 root disk 254,  7 2007-01-10 12:52 /dev/dm-7
crw-rw---- 1 root root  10, 63 2007-01-10 12:51 /dev/mapper/control
brw-rw---- 1 root disk 254,  0 2007-01-10 12:51 /dev/mapper/strider-swap
brw-rw---- 1 root disk 254,  1 2007-01-10 12:52 /dev/mapper/strider-root
brw-rw---- 1 root disk 254,  2 2007-01-10 12:52 /dev/mapper/strider-usr
brw-rw---- 1 root disk 254,  3 2007-01-10 12:52 /dev/mapper/strider-var
brw-rw---- 1 root disk 254,  4 2007-01-10 12:51 /dev/mapper/strider-home
brw-rw---- 1 root disk 254,  5 2007-01-10 12:52 /dev/mapper/strider-srv
brw-rw---- 1 root disk 254,  6 2007-01-10 12:52 /dev/mapper/strider-home_crypt
brw-rw---- 1 root disk 254,  7 2007-01-10 12:52 /dev/mapper/strider-swap_crypt

After it has run, I have:
brw-rw---- 1 root disk 254,  0 2007-01-10 12:51 /dev/dm-0
brw-rw---- 1 root disk 254,  1 2007-01-10 12:51 /dev/dm-1
brw-rw---- 1 root disk 254,  2 2007-01-10 12:51 /dev/dm-2
brw-rw---- 1 root disk 254,  3 2007-01-10 12:51 /dev/dm-3
brw-rw---- 1 root disk 254,  4 2007-01-10 12:51 /dev/dm-4
brw-rw---- 1 root disk 254,  5 2007-01-10 12:51 /dev/dm-5
brw-rw---- 1 root disk 254,  6 2007-01-10 12:52 /dev/dm-6
brw-rw---- 1 root disk 254,  7 2007-01-10 12:52 /dev/dm-7
crw-rw---- 1 root root  10, 63 2007-01-10 12:51 /dev/mapper/control
brw-rw---- 1 root disk 254,  0 2007-01-10 12:51 /dev/mapper/strider-swap
brw-rw---- 1 root disk 254,  1 2007-01-10 12:52 /dev/mapper/strider-root
brw-rw---- 1 root disk 254,  2 2007-01-10 12:52 /dev/mapper/strider-usr
brw-rw---- 1 root disk 254,  3 2007-01-10 12:52 /dev/mapper/strider-var
brw-rw---- 1 root disk 254,  4 2007-01-10 12:51 /dev/mapper/strider-home
brw-rw---- 1 root disk 254,  5 2007-01-10 12:52 /dev/mapper/strider-srv

This remains unchanged after S50lvm has been run, so lvm-common also
fails to remove its /dev/mapper/ device nodes for LVs that have been
brought down (all except strider-root and dm-1).

The dm-* devices are only being created since recently after a recent
change in udev (0.103-1):
* udev.rules, devfs.rules: stop suppressing creation of dm-* devices,
  because they are needed by HAL. (Closes: #392623)

The problem seems to be nothing takes responsibility for removing them.
I'm not sure if that should be device mapper, or udev, or cryptsetup and
lvm-common.

If device nodes are _not_ supposed to be removed, then I guess the
original report is still valid and the lvm tools should not complain
about devices that do not exist (anymore).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20070110/86f59e3c/attachment.pgp


More information about the pkg-lvm-maintainers mailing list