Bug#640816: dmsetup: wrong DM_NAME on removable device

Yves-Alexis Perez corsac at debian.org
Wed Sep 7 16:41:55 UTC 2011


Package: dmsetup
Version: 2:1.02.65-1
Severity: normal

Hey,

I have an issue with (I guess) dmsetup udev rules.

I have an encrypted luks root, which is enabled with the name
scapa_crypt:

lrwxrwxrwx 1 root root 7  7 sept. 18:03 /dev/mapper/scapa_crypt -> ../dm-0

and dmsetup sees it:

sudo dmsetup info scapa_crypt
Name:              scapa_crypt
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        3
Event number:      0
Major, minor:      254, 0
Number of targets: 1
UUID: CRYPT-LUKS1-480bf4e951054d47a75c4f716db96c25-scapa_crypt

and udev see the correct variables:

sudo udevadm info --path /sys/block/dm-0 --query=all
P: /devices/virtual/block/dm-0
N: dm-0
S: mapper/scapa_crypt
E: UDEV_LOG=3
E: DEVPATH=/devices/virtual/block/dm-0
E: MAJOR=254
E: MINOR=0
E: DEVNAME=/dev/dm-0
E: DEVTYPE=disk
E: SUBSYSTEM=block
E: DM_NAME=scapa_crypt
E: UDISKS_PRESENTATION_HIDE=1
E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
E: DM_UDEV_DISABLE_DISK_RULES_FLAG=1
E: DM_UDEV_DISABLE_OTHER_RULES_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UUID=CRYPT-LUKS1-480bf4e951054d47a75c4f716db96c25-scapa_crypt
E: DM_SUSPENDED=0
E: UDISKS_PRESENTATION_NOPOLICY=1
E: DEVLINKS=/dev/mapper/scapa_crypt

Now, when I plug a usb key or any removable device to the system,
dmsetup udev rules (I guess) seem to mess something and add some of the
variables to that device:

sudo udevadm info --path /sys/block/sdb/sdb1 --query=all
P: /block/sdb/sdb1
N: sdb1
S: disk/by-id/usb-Kingston_DataTraveler_2.0_5B84090002AD-0:0-part1
S: disk/by-path/pci-0000:00:1d.0-usb-0:1.2:1.0-scsi-0:0:0:0-part1
S: disk/by-uuid/ab312548-63c6-4b67-bb13-f32ee310c78a
S: disk/by-label/boot
E: UDEV_LOG=3
E: DEVPATH=/block/sdb/sdb1
E: MAJOR=8
E: MINOR=17
E: DEVNAME=/dev/sdb1
E: DEVTYPE=partition
E: SUBSYSTEM=block
E: DM_NAME=scapa_crypt <=== THIS
E: UDISKS_PRESENTATION_HIDE=1
E: ID_VENDOR=Kingston
E: ID_VENDOR_ENC=Kingston
E: ID_VENDOR_ID=13fe
E: ID_MODEL=DataTraveler_2.0
E: ID_MODEL_ENC=DataTraveler\x202.0
E: ID_MODEL_ID=1f00
E: ID_REVISION=PMAP
E: ID_SERIAL=Kingston_DataTraveler_2.0_5B84090002AD-0:0
E: ID_SERIAL_SHORT=5B84090002AD
E: ID_TYPE=disk
E: ID_INSTANCE=0:0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=pci-0000:00:1d.0-usb-0:1.2:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_1d_0-usb-0_1_2_1_0-scsi-0_0_0_0
E: ID_PART_TABLE_TYPE=dos
E: ID_FS_LABEL=boot
E: ID_FS_LABEL_ENC=boot
E: ID_FS_UUID=ab312548-63c6-4b67-bb13-f32ee310c78a
E: ID_FS_UUID_ENC=ab312548-63c6-4b67-bb13-f32ee310c78a
E: ID_FS_VERSION=1.0
E: ID_FS_TYPE=ext2
E: ID_FS_USAGE=filesystem
E: ID_PART_ENTRY_SCHEME=dos
E: ID_PART_ENTRY_TYPE=0x83
E: ID_PART_ENTRY_FLAGS=0x80
E: ID_PART_ENTRY_NUMBER=1
E: UDISKS_PRESENTATION_NOPOLICY=0
E: UDISKS_PARTITION=1
E: UDISKS_PARTITION_SCHEME=mbr
E: UDISKS_PARTITION_NUMBER=1
E: UDISKS_PARTITION_TYPE=0x83
E: UDISKS_PARTITION_SIZE=128120832
E: UDISKS_PARTITION_FLAGS=boot
E:
UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/host16/target16:0:0/16:0:0:0/block/sdb
E: UDISKS_PARTITION_OFFSET=7168
E: UDISKS_PARTITION_ALIGNMENT_OFFSET=0
E:
DEVLINKS=/dev/disk/by-id/usb-Kingston_DataTraveler_2.0_5B84090002AD-0:0-part1
/dev/disk/by-path/pci-0000:00:1d.0-usb-0:1.2:1.0-scsi-0:0:0:0-part1
/dev/disk/by-uuid/ab312548-63c6-4b67-bb13-f32ee310c78a
/dev/disk/by-label/boot

I have no idea why the DM_NAME (and DM_UUID sometimes) is the same, but
this looks very weird. And the same thing happens with other usb keys,
sd card etc.

It's really annoying since I'd like to hide the encrypted partition in
my drive using a custom rule but doesn't really want to hide other
stuff.

Regards,
-- 
Yves-Alexis
-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dmsetup depends on:
ii  libc6               2.13-18    
ii  libdevmapper1.02.1  2:1.02.65-1
ii  libudev0            172-1      
ii  util-linux          2.19.1-5   

dmsetup recommends no packages.

dmsetup suggests no packages.

-- no debconf information





More information about the pkg-lvm-maintainers mailing list