drbd with only 2 disks

[mrshark]

lvm, as it resides ON drbd, must start AFTER it! So:

update-rc.d -f lvm2 remove
update-rc.d lvm2 start 80 2 3 4 5 . stop 20 0 1 6 .

i installed the latest pve version, 1.5, with 2.6.32, on top of debian lenny, and still this problems occur... in standard installation, drbd starts after lvm, so lvm does not start well on both nodes...

so, cat /proc/drbd gives UPDATED/UPDATED but pvdisplay returns a phisical volume only on master node, until i restart lvm or force a pvscan... or, using my method to start lvm AFTED drbd...

 

[dietmar]

i installed the latest pve version, 1.5, with 2.6.32, on top of debian lenny, and still this problems occur... in standard installation, drbd starts after lvm, so lvm does not start well on both nodes...

Maybe you forgot to set the lvm filter?

 

[mrshark]

no, filter is ok...

clu1:~# cat /etc/lvm/lvm.conf |grep filter|grep -v "#"
    filter = [ "r|/dev/sda3|", "r|/dev/disk/|", "r|/dev/block/|", "a/.*/" ]
clu1:~# ssh clu2 -C cat /etc/lvm/lvm.conf |grep filter|grep -v "#"
    filter = [ "r|/dev/sda3|", "r|/dev/disk/|", "r|/dev/block/|", "a/.*/" ]

 

[dietmar]

drbd starts after lvm, so lvm does not start well on both nodes...

Why is that a problem? LVM VGs are automatically detected.

 

[mrshark]

Why is that a problem? LVM VGs are automatically detected.

i've just said that with standard startup order, if i go on second node, not master, pvdisplay, vgdisplay and lvdisplay ALL return absolutely nothing... with my modification to order, they work as expected, instead... this is the question: why this do not work as you say? if i need to do a pvscan to make them available, then is better my solution, that does not require further intervention by me...

 

[dietmar]

i've just said that with standard startup order, if i go on second node, not master, pvdisplay, vgdisplay and lvdisplay ALL return absolutely nothing... with my modification to order, they work as expected, instead... this is the question: why this do not work as you say? if i need to do a pvscan to make them available, then is better my solution, that does not require further intervention by me...

As soon as you use the storage (for examply by starting a VM) it is activated? If not, it is a bug.

 

[mrshark]

is it now possible to have this setup using the new installation iso, or it's needed to continue to go via the path of debian with custom partitioning and adding repositories after installation?