Issue #2843 has been updated by tkusumi.
dm_dev_lookup_uuid() returning non null for the second dmsetup create seems to be the reason for EEXIST. The original Linux kernel implementation doesn't have this uuid logic, so this behavior seems to be (net)bsd specific. This behavior doesn't make sense (at least to me), but not sure if this should be fixed nor is it trivial, so just leave it as it is for now. ---------------------------------------- Bug #2843: Fails to create dm device via dmsetup http://bugs.dragonflybsd.org/issues/2843#change-12708 * Author: tkusumi * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- There seems to be an issue with device mapper on dfly. This happens with dm-error target as well. I'll try to investigate and fix when possible (since I want dm-flakey on dfly). ---------- # uname Linux # dmsetup create zero1 --table '0 100 zero' # ls -l /dev/mapper/zero* lrwxrwxrwx 1 root root 7 Sep 29 00:14 /dev/mapper/zero1 -> ../dm-3 # dmsetup create zero2 --table '0 100 zero' # ls -l /dev/mapper/zero* lrwxrwxrwx 1 root root 7 Sep 29 00:14 /dev/mapper/zero1 -> ../dm-3 lrwxrwxrwx 1 root root 7 Sep 29 00:14 /dev/mapper/zero2 -> ../dm-4 ---------- # uname DragonFly # kldload dm # dmsetup create zero1 --table '0 100 zero' # ls -l /dev/mapper/zero* crw-r----- 1 root operator 66, 0x1e110007 Sep 29 00:01 /dev/mapper/zero1 # dmsetup create zero2 --table '0 100 zero' ioctl create call failed: File exists Command failed # ls -l /dev/mapper/zero* crw-r----- 1 root operator 66, 0x1e110007 Sep 29 00:01 /dev/mapper/zero1 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
