Hello,
I have a volume group with 20 logical volumes. Only the last one of
these volumes has a strange problem with dmsetup, shown by these
commands and output on the command line:
root@host:/home/linux# /sbin/dmsetup info -c -o name --noheadings
/dev/vg/lv20
Device does not exist.
Command
Hello,
I did not know dmsetup works with lvm file names, did you try to run `dmsetup
ls` to see the known devices and the dm compatible name?
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: linux-lvm-boun...@redhat.com im Auftrag von Zdenek Kabelac
Gesendet:
Dne 14. 08. 19 v 9:22 Christoph Pleger napsal(a):
Hello,
I have a volume group with 20 logical volumes. Only the last one of these
volumes has a strange problem with dmsetup, shown by these commands and
output on the command line:
root@host:/home/linux# /sbin/dmsetup info -c -o name --nohead
Dne 13. 08. 19 v 23:25 Bernd Eckenfels napsal(a):
Hello,
I did not know dmsetup works with lvm file names, did you try to run `dmsetup
ls` to see the known devices and the dm compatible name?
Hi
Of course it has to work.
lvm2 names are just symlinks to /dev/dm-XXX real device nodes.
If sym
Hello,
So are you actually trying to access not a 'normal' LV - but an LV
under snapshot ?
No, /dev/vg/lv20 is a normal logical volume. But /dev/vg/lv15 has been
under snapshot before.
Now, I created a snapshot manually (before. it was created by an
automatic backup mechanism) and saw what
Hello,
and you can enable verification of udev rule
processing with lvm.conf option:
verify_udev_operations = 1
after setting this, I got the following message from lvremove:
Node /dev/mapper/vg-lv15-real was not removed by udev. Falling back to
direct node removal.
Regards
Chri