[DRBD-user] Having Trouble with LVM on DRBD

Igor Cicimov icicimov at gmail.com
Mon Feb 29 22:47:24 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 01/03/2016 3:08 AM, "Eric Robinson" <eric.robinson at psmnv.com> wrote:
> >> That approach does not really work because if you stop resource
> >> p_mysql_002 (for example) then all the other resources in the group
stop too!
> >>
> > Still dont understand whats your problem with that.
> Each mysql instance is for a different customer. If I need to stop or
restart one customer's database, or remove the resource from the group
(perhaps because I lost the customer or I need to move their database to a
different server for load distribution), then I don't all the other
customers' databases going down too!

It's just a matter of design, the way you have it setup atm will not work
of course. If you have them set as in my example:

group g_drbd0 p_lvm_drbd0 p_fs_clust1 p_vip_clust1 p_mysql_001
group g_drbd1 p_lvm_drbd1 p_fs_clust2 p_vip_clust2 p_mysql_002
group g_drbd99 p_lvm_drbd99 p_fs_clust100 p_vip_clust100 p_mysql_100

then each mysql instance gets its own VIP instead of shared one as in your
case. Then during migration you move the group and the backing drbd device
will get promoted to master on the other node and the whole group will

There are many ways to skin the cat.

> --Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160301/0ca67816/attachment.htm>

More information about the drbd-user mailing list