I have two nodes with /dev/drbd0 as a physical volume and volume group "replicated" on it.
When i create or rename logical volume in vg "replicated" on one node, it's appear on another, but only in the output of lvdisplay/lvscan/lvs.
/dev/replicated/ and /dev/mapper stays unchanged and live migration with such logical volumes not working. How to enforce device-mapper to reread logical volumes in volumegroup and recreate device nodes in /dev/mapper and symlinks in /dev/replicated?
vgchange -a n replicated && vgchange -a y replicated works for me, but it is too destructive...
PLEASE, help me. i need to recover my volume group after modifying metadata with standard lvm utilities, not with proxmox lvm metadata locking system (which is similar to clvm)
When i create or rename logical volume in vg "replicated" on one node, it's appear on another, but only in the output of lvdisplay/lvscan/lvs.
/dev/replicated/ and /dev/mapper stays unchanged and live migration with such logical volumes not working. How to enforce device-mapper to reread logical volumes in volumegroup and recreate device nodes in /dev/mapper and symlinks in /dev/replicated?
vgchange -a n replicated && vgchange -a y replicated works for me, but it is too destructive...
PLEASE, help me. i need to recover my volume group after modifying metadata with standard lvm utilities, not with proxmox lvm metadata locking system (which is similar to clvm)
Last edited: