On Mon, Feb 9, 2009 at 11:22 AM, Manfred Hollstein <manfred@die-hollsteins.de> wrote:
No, it's _not_ a workaround, it's the proper solution!
got it. for my case, i've on /dev/md0 -> '/boot' /dev/md1 -> VG('VG_Swap'):LV('LV_SWAP'):'swap' /dev/md2 -> VG('VG_Dom0'):LV('LV_ROOT'):'/' /dev/md3 -> VG('VG_DomU'):LV('work'):'/home/work' :LV('xen'):'/home/xen' (fwiw, i keep my xen configs here) reading lvm.conf (& man), using the default lvm.conf's 'filter = [...]', @ rm /etc/lvm/.cache && vgs WARNING: Duplicate VG name vg0:... <------ WARNINGS etc ... VG_Dom0 ... VG_DomU ... VG_Swap ... changing to, filter =[ "a|/dev/md[12]|", "r|.*|" ] i.e., *excluding* /dev/md3 containing VG_DomU, @, rm /etc/lvm/.cache && vgs VG_Dom0 ... VG_Swap ... as expected. but, of course, since i create new xen DomU images in/on VG_DomU's remaining space, dd, lvcreate -n new_DomU -L 4G /dev/VG_DomU dd if=/dev/VG_DomU/domu_template of=/dev/VG_DomU/new_DomU @ 'dd', Volume group "VG_DomU" not found since the /dev/md3 block dev, on which VG_DomU resides, is not included iiuc, the 'filter=' specification filters on block-devices only, not VG/LV names (at least i've not figured out a regex that works, yet). yet, the UUID/name conflicts I'm seeing _are_ on names. _can_ i exclude the DomU images from scanning by LVM @ 'xm create' time if they share a block-dev with other VG's that are to be scanned? if yes, what regex would work here? given your comment,
In your case the files containing the LVM signatures (which are scanned for when /etc/init.d/boot.lvm runs) *will* be found unless you exclude them from this process.
it seems i can/might exclude individual files? -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org