logical volume is set to inactive after reboot

Discussion in 'Installation/Configuration' started by Tomislav Aurednik, Mar 31, 2017.

  1. I've got a big problem that I can't find a fix (trying 3 days allready). I have a lv that I want to use for DRBD. Until I don't install drbd8-utils and set the configuration the lv acts normally. By this I mean it stays active. After I create my resourse that uses this lv and put it up it get set to inactive after reboot. I'm useing Ubuntu 16.04 LTS server.

    My drbd config (/etc/drbd.d/mysql.res) is:
    resource mysql
    {
    on tmysql1
    {
    device /dev/drbd0;
    disk /dev/mapper/vg--vda-lv--drbd0;
    address 10.0.0.11:7790;
    meta-disk internal;
    }
    on tmysql2
    {
    device /dev/drbd0;
    disk /dev/mapper/vg--vda-lv--drbd0;
    address 10.0.0.12:7790;
    meta-disk internal;
    }
    }
    The protocol and usage is set in the global config. I've tryed using for disk /dev/vg-vda/lv-drbd0; and it's the same.
    The "funny" thing is that this is happening on the second pair of node servers. On the first pair everything works! Can someone please help?
     
  2. I sent a sosreport and lvmdump to linbit, maybe they'll figure out the cause of the probelm.
    My tmp fix is adding a line to /etc/rc.local.
    /sbin/vgchange -ay
     

Share This Page