[DRBD-user] Having Trouble with LVM on DRBD

Igor Cicimov icicimov at gmail.com
Fri Feb 26 01:22:09 CET 2016

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


On Fri, Feb 26, 2016 at 10:37 AM, Eric Robinson <eric.robinson at psmnv.com>
wrote:

> > Those are not the backing devices. Backing devices are the ones named
> > on the "disk " lines in your DRBD resource files - for example "disk
> /dev/vg/lv1".
>
> Sorry, for a second I was thinking of the drbd disks as backing devices
> for the LVM volumes that were created on them, but you're absolutely right.
>
> > So you need to exclude /dev/vg/lv1 (in that example) from being looked
> > at by LVM by filtering it out.
>
> On my servers, I have /dev/vg00/lv01 and /dev/vg00/lv02, which are the
> backing devices for /dev/drbd0 and /dev/drbd1 respectively. Then I made
> drbd0 and drbd1 into PVs, and created logical volume /dev/vg_drbd0/lv_drbd0
> on drbd0, and /dev/vg_drbd1/lv_drbd1 on drbd1.
>
> You're saying that I should filter /dev/vg00/lv01 and /dev/vg00/lv02 in
> lvm.conf? That won't have any undesirable side effects?
>
> --Eric
>
> Maybe this will help. In my case I have:

...
filter = [ "a|/dev/vd.*|", "a|/dev/drbd*|", "r|.*|" ]
write_cache_state = 0
volume_list = [ "rootvg", "vg1", "vg2" ]
...

so in your case, you need to replace */dev/vd.** with the *block device*
your *root volume* *vg00* lives on, ie /dev/sda or what ever device your
vg00 has been carved from.



>
>
>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160226/3d2d4f4b/attachment.htm>


More information about the drbd-user mailing list