Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.# lvcreate -l 254 -T vg3/pool-01 2.# ls -l /dev/mapper/vg3* lrwxrwxrwx. 1 root root 8 Apr 16 02:05 /dev/mapper/vg3-pool--01 -> ../dm-45 lrwxrwxrwx. 1 root root 8 Apr 16 02:05 /dev/mapper/vg3-pool--01_tdata -> ../dm-43 lrwxrwxrwx. 1 root root 8 Apr 16 02:05 /dev/mapper/vg3-pool--01_tmeta -> ../dm-42 lrwxrwxrwx. 1 root root 8 Apr 16 02:05 /dev/mapper/vg3-pool--01-tpool -> ../dm-44 3.# lvs vg3 LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert pool-01 vg3 twi-a-tz 1016.00m 0.00 Actual results: /dev/mapper/vg3-pool--01 Expected results: /dev/mapper/vg3-pool-01 Additional info:
this issue was encountered if the lv name has '-'
This is not a bug. The '-' character is doubled if it's part of the volume name (or volume group name). The character is escaped this way because, otherwise, the '-' character alone is considered as a delimiter between a VG name and an LV name.
The supported form for other software to use is '/dev/vg3/pool-01'. /dev/mapper/* and /dev/dm-* are considered private internal names.
(And in the case of thin pools, they will usually be considered private and not meant to be used by other software, so not available under /dev/vg*.)