Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello Lars,
thanks for the -vvv tip.
I had used -v (documented in vgcreate manpage), but that was not enough...
vgcreate -vvv had this output:
[...]
/dev/md7: lvm2 label detected
Closed /dev/md7
Duplicate PV 0biBqFWpblfkDfY2KOsejWzERVPNngxq on /dev/drbd1 -
using md /dev/md7
[...]
excluding all md devices in /etc/lvm/lvm.conf and deleting
/etc/lvm/.cache fixed the problem.
Thanks again.
Matthias
P.S. sorry for the PM - I used the wrong reply.
Lars Ellenberg wrote:
> / 2006-02-16 20:05:02 +0100
> \ Matthias Weigel:
>
>># vgcreate fth /dev/drbd1
>> Volume group "fth" successfully created
>>
>># vgdisplay
>>
>># vgdisplay fth
>> Volume group "fth" doesn't exist
>>
>># lvcreate -L512M -nfailover fth
>> Volume group "fth" doesn't exist
>>
>>Why does vgcreate report success, but the VG is NOT here?
>>
>>This seems to be a DRBD problem. Using /dev/md7 instead of /dev/drbd1 works.
>>
>>Any Idea?
>
>
> run the lvm tools with -vvv
> run them under strace
> see whether they try at all to access the drbd.
> see whether they get confused by something
> after all, drbd is transparent, and so is md.
> lvm tools special case md, but probably forget
> to special case drbd as well.
>