Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
I tried to setup LVM2 over DRBD over MD-Raid1.
The tests were done in Vmware virtual machines, WBEL4, kernel 2.6.9-22.0.1.
# fdisk -l /dev/sdc
Disk /dev/sdc: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 130 1044193+ fd Linux raid
autodetect
# cat /proc/mdstat
Personalities : [raid1]
md7 : active raid1 sdc1[0]
1044096 blocks [1/1] [U]
# cat /proc/drbd
version: 0.7.14 (api:77/proto:74)
SVN Revision: 1989 build by root at fth1.maweos.de, 2005-12-18 17:02:43
0: cs:Connected st:Primary/Secondary ld:Consistent
ns:4 nr:4 dw:8 dr:261 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
1: cs:Connected st:Primary/Secondary ld:Consistent
ns:913064 nr:0 dw:14732 dr:913840 al:8 bm:56 lo:0 pe:0 ua:0 ap:0
# pvdisplay
# pvcreate /dev/drbd1
Physical volume "/dev/drbd1" successfully created
# pvdisplay
--- NEW Physical volume ---
PV Name /dev/drbd1
VG Name
PV Size 891.44 MB
Allocatable NO
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID 0biBqF-Wpbl-fkDf-Y2KO-sejW-zERV-PNngxq
# 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?
Best Regards
Matthias Weigel