[DRBD-user] Testing new DRBD9 dedicated repo for PVE

[Roberto Resoli]

Il 09/01/2017 10:56, Roberto Resoli ha scritto:
> Il 29/12/2016 15:01, Roberto Resoli ha scritto:
>> Il 28/12/2016 16:00, Roberto Resoli ha scritto:
>>> Il 27/12/2016 10:19, Roberto Resoli ha scritto:
>>>> All is up and running nicely, in any case.
>> Another issue: drbdmanaged starts at boot, but most resources remain down; a
>>
>> drbdmanaged restart
>>
>> fixes that.
>>
>> I attach a related fragment from syslog; it seems that some temporary
>> .res files are not generated correctly.
> 
> any hint?

After having upgraded to python-drbdmanage 0.99.1-1 from linbit drbd9
repo for proxmox, a simple

drbdmanage restart

does not fixes the situation anymore, the "start" part failing most of
times.

The only way to recover I found is  to issue a

drbdmanage export-res "*"

and issuing manually a

drbdadm up <resource>

for every <resource>

I attach a fragment of syslog while a pve node restart; note that at
least one resource ('vm-101-disk-1') is coming up correctly, the other
are failing because (it appears to me) of incorrect temporary resources
definition.

Here two examples of exported defintion ('vm-101-disk-1' is first):

==========
# This file was generated by drbdmanage(8), do not edit manually.
#dm-meta:{}

resource vm-101-disk-1 {
template-file "/var/lib/drbd.d/drbdmanage_global_common.conf";

   net {
       allow-two-primaries yes;
       shared-secret "XEDTfmZotteF377OlXOA";
       max-epoch-size 8000;
       cram-hmac-alg sha1;
       max-buffers 8000;
   }
   connection-mesh {
      hosts pve1 pve3 pve2;
   }
    on pve1 {
        node-id 0;
        address ipv4 10.1.1.1:7001;
        volume 0 {
            device minor 101;
            disk /dev/drbdpool/vm-101-disk-1_00;
            disk {
                size 4194304k;
            }
            meta-disk internal;
        }
    }
    on pve3 {
        node-id 2;
        address ipv4 10.1.1.3:7001;
        volume 0 {
            device minor 101;
            disk /dev/drbdpool/vm-101-disk-1_00;
            disk {
                size 4194304k;
            }
            meta-disk internal;
        }
    }
    on pve2 {
        node-id 1;
        address ipv4 10.1.1.2:7001;
        volume 0 {
            device minor 101;
            disk /dev/drbdpool/vm-101-disk-1_00;
            disk {
                size 4194304k;
            }
            meta-disk internal;
        }
    }
}
==========
# This file was generated by drbdmanage(8), do not edit manually.
#dm-meta:{"create_date": "2017-01-10T09:47:11.089762"}

resource vm-105-disk-1 {
template-file "/var/lib/drbd.d/drbdmanage_global_common.conf";

   net {
       allow-two-primaries yes;
       shared-secret "MYNxm7S4qx3zeoJPTrk9";
       cram-hmac-alg sha1;
   }
   connection-mesh {
      hosts pve1 pve3 pve2;
   }
    on pve1 {
        node-id 1;
        address ipv4 10.1.1.1:7010;
        volume 0 {
            device minor 110;
            disk /dev/drbdpool/vm-105-disk-1_00;
            disk {
                size 4194304k;
            }
            meta-disk internal;
        }
    }
    on pve3 {
        node-id 2;
        address ipv4 10.1.1.3:7010;
        volume 0 {
            device minor 110;
            disk /dev/drbdpool/vm-105-disk-1_00;
            disk {
                size 4194304k;
            }
            meta-disk internal;
        }
    }
    on pve2 {
        node-id 0;
        address ipv4 10.1.1.2:7010;
        volume 0 {
            device minor 110;
            disk /dev/drbdpool/vm-105-disk-1_00;
            disk {
                size 4194304k;
            }
            meta-disk internal;
        }
    }
}




-------------- next part --------------
A non-text attachment was scrubbed...
Name: drbd9_failing_resources.log.gz
Type: application/gzip
Size: 2169 bytes
Desc: not available
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20170216/85ebec18/attachment.bin>