[DRBD-user] r0 ok, r1 PingAck did not arrive in time

Louis mailtolouis2020-forum at yahoo.com
Wed Jun 26 16:06:38 CEST 2013

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


Hi,

We had the same problem before, upgrade to Ubuntu 13.04 solved the problem.




>________________________________
> From: Gerald Brandt <gbr at majentis.com>
>To: drbd-user at lists.linbit.com 
>Sent: Wednesday, June 26, 2013 12:20 PM
>Subject: Re: [DRBD-user] r0 ok, r1 PingAck did not arrive in time
> 
>
>Sorry, that should have been Ubuntu 12.10
>
>Gerald
>
>----- Original Message -----
>> From: "Gerald Brandt" <gbr at majentis.com>
>> To: drbd-user at lists.linbit.com
>> Sent: Wednesday, June 26, 2013 6:09:06 AM
>> Subject: Re: [DRBD-user] r0 ok, r1 PingAck did not arrive in time
>> 
>> Hi,
>> 
>> I'm having the same issue with Ubuntu 12.04 LTS (kernel 3.5.0) and
>> DRBD 8.3.13, and I'm thinking of adding a third DRBD resource to the
>> same box.
>> 
>> Gerald
>> 
>> 
>> ----- Original Message -----
>> > From: "Lukas Gradl" <proxmox at ssn.at>
>> > To: drbd-user at lists.linbit.com
>> > Sent: Tuesday, June 25, 2013 3:31:51 PM
>> > Subject: [DRBD-user] r0 ok, r1 PingAck did not arrive in time
>> > 
>> > Hi!
>> > 
>> > I've a two-node cluster with two identical configured ressources.
>> > The
>> > first resource (r0) works like a charm, r1 gets "PingAck did not
>> > arrive in time" after 30min. maximum which results in a split-brain
>> > situation.
>> > 
>> > I'm using DRBD 8.3.10 with kernel 2.6.32 on a debian squeeze using
>> > proxmox for virtualization.
>> > The connection between the two nodes is bonding device built out of
>> > two Intel e1000 cards.
>> > 
>> > Here's the resource definition of my drbd.conf
>> > 
>> > resource r0 {
>> >          protocol C;
>> >          disk {
>> >                  no-md-flushes;
>> >                  no-disk-flushes;
>> >                  no-disk-barrier;
>> >          }
>> >          on vm01 {
>> >                  device /dev/drbd0;
>> >                  disk /dev/sdb1;
>> >                  address 10.254.1.101:7780;
>> >                  meta-disk internal;
>> >          }
>> >          on vm02 {
>> >                  device /dev/drbd0;
>> >                  disk /dev/sdb1;
>> >                  address 10.254.1.102:7780;
>> >                  meta-disk internal;
>> >          }
>> > }
>> > resource r1 {
>> >          protocol C;
>> >          disk {
>> >                  no-md-flushes;
>> >                  no-disk-flushes;
>> >                  no-disk-barrier;
>> >          }
>> >          on vm01 {
>> >                  device /dev/drbd1;
>> >                  disk /dev/sdc2;
>> >                  address 10.254.1.101:7781;
>> >                  meta-disk internal;
>> >          }
>> >          on vm02 {
>> >                  device /dev/drbd1;
>> >                  disk /dev/sdc2;
>> >                  address 10.254.1.102:7781;
>> >                  meta-disk internal;
>> >          }
>> > }
>> > 
>> > 
>> > any help anyone?
>> > 
>> > regards
>> > Lukas
>> > --
>> > 
>> > --------------------------
>> > software security networks
>> > Lukas Gradl <proxmox#ssn.at>
>> > Eduard-Bodem-Gasse 6
>> > A - 6020 Innsbruck
>> > Tel: +43-512-214040-0
>> > Fax: +43-512-214040-21
>> > --------------------------
>> > _______________________________________________
>> > drbd-user mailing list
>> > drbd-user at lists.linbit.com
>> > http://lists.linbit.com/mailman/listinfo/drbd-user
>> > 
>> _______________________________________________
>> drbd-user mailing list
>> drbd-user at lists.linbit.com
>> http://lists.linbit.com/mailman/listinfo/drbd-user
>> 
>_______________________________________________
>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/20130626/6e0c4aa6/attachment.htm>


More information about the drbd-user mailing list