I'm told that /dev/VG/LV is the official LVM syntax for a devname,
so I passed a /dev/VG/LV, name to LVM, and it mangled the LV name,
splitting it into a LVLayer.
I gave it:
/dev/Home+Space/Home-2011.08.08-03.29.58
Which corresponds to a /home/snapdir/@GMT-2011.08.08-03.29.58
(@GMT-date-time is a required name format), so my volumes
for such snapdirs have the base-LV and the date-time.
There is nothing in the lvm spec that or device name spec, that says
"-" is to be interpreted as some layer....
The problem is that when this routine gets a device name, it might be
/dev/mapper/<encoded value>
or /dev/VG/LV
dmsetup splitname, should, I believe, know how to split
names in the only 'supported' name format i.e. /dev/VG/LV -- but
instead, it's treating it as though it were under /dev/mapper and using
that for
decoding...
I can hack around the bug, but its surprising that dmsetup doesn't support
the only official LVM names (/dev/VG/LV).
Is this bug a 'feature', or is it something that should be fixed?
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
