Comment 13 for bug 483890

Clint Byrum (clint-fewbar) wrote :

So, on inspecting this on hardy (I know the original report was against karmic), I have no /lib/udev/rules.d, and my /etc/udev/rules.d/65-dmsetup.rules looks like this:

# This file causes devicemapper devices to be assigned names by udev
# based on the name given to dmsetup.
# See udev(8) for syntax.

SUBSYSTEM!="block", GOTO="dmsetup_end"
KERNEL!="dm-*", GOTO="dmsetup_end"
ACTION!="add|change", GOTO="dmsetup_end"

# Obtain device status
IMPORT{program}="/sbin/dmsetup export -j%M -m%m"
ENV{DM_NAME}!="?*", GOTO="dmsetup_end"

# Make the device take the /dev/mapper name
OPTIONS+="string_escape=none", NAME="mapper/$env{DM_NAME}"
ENV{DM_UUID}=="?*", SYMLINK+="disk/by-id/dm-uuid-$env{DM_UUID}"

# Skip vol_id for suspended devices and those with empty or error tables
ENV{DM_STATE}=="SUSPENDED", GOTO="dmsetup_end"
ENV{DM_TARGET_TYPES}=="|*error*", GOTO="dmsetup_end"

# by-uuid and by-label symlinks
IMPORT{program}="vol_id --export $tempnode"
ENV{DM_TARGET_TYPES}=="*snapshot-origin*", OPTIONS="link_priority=-90"
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", \
ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", \


And I'm not seeing any messages from udev on running the '' script (modified to fit inside my 10G test vm image).

Given that karmic is nearly EOL, I'm not all that interested in trying to reproduce it on karmic. Can one of the other users confirm that bug #241109 is in fact a duplicate of this, or are they separate issues (given that it is against hardy, not karmic).