[DRBD-user] Rescanning LVM after DRBD starts on CentOS 5

Digimer linux at alteeve.com
Thu May 20 19:09:59 CEST 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On 10-05-20 01:13 AM, Ben Timby wrote:
> On Wed, May 19, 2010 at 8:21 PM, Digimer<linux at alteeve.com>  wrote:
>> Hi all,
>>
>>   I've got a Primary/Primary setup running on a simple 2-node cluster running
>> CentOS 5.5 x86_64. The DRBD devices are LVM LVs on either node. The DRBD
>> itself is, in turn, a PV which hosts a VG and a couple LVs used in the
>> cluster.
>>
>>   This all works and everything is fine. The problem is that when the nodes
>> boot, the DRBD-based PV (and thus it's VG and LVs) are no visible. This is
>> easy enough to fix by running the following on both nodes:
>>
>> pvscan
>> vgscan
>> lvscan
>> lvchange -a y /dev/drbd_vg0/iso_store /dev/drbd_vg0/vm01
>>
>>   I know the second node doesn't need to call 'lvchange'...
>>
>>   Anyway, my question is; How do I get LVM to automatically recognize the
>> DRBD-based LVM components at boot time? The reason I want to sort this out
>> is that I want to be able to add my GFS LV to /etc/fstab so that the system
>> comes up on it's own on boot (even if the other node is off).
>>
>>   Should I be asking this on the LVM mailing list? I figured it's more
>> appropriate here as not so many LVM users use DRBD as the other way around.
>> :)
>
> I have a similar setup on CentOS 5.4 using Pacemaker. Use the LVM RA,
> it will handle this for you. Just make it start after your DRBD
> resource, and it will scan after DRBD comes up.

LVM RA is what, exactly? I tried googling it and found patches, but no 
reference to any programs, config files or what-have-you.

Thanks!

-- 
Digimer
E-Mail:         linux at alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org



More information about the drbd-user mailing list