Mailing List Archive: drbd raid stays at state peer: Connecting

drbd raid stays at state peer: Connecting

Oct 17, 2021, 1:52 AM

Post #1 of 3 (510 views)

Hello,

on two servers, I created two drbd resources, where one server is the
primary for the first resource and the other server is the primary for
the second resource. A dump of my setup is attached.

Unfortunately, the drbd RAID works for the first resource, but it does
not for the second. "drbdadm status" since almost two days now shows on
the first machine:

grobi role:Primary
volume:2 disk:UpToDate
peer role:Secondary

volume:2 replication:Established peer-disk:UpToDate

hastig
role:Secondary
volume:1 disk:Inconsistent
volume:3 disk:Inconsistent

volume:4 disk:Inconsistent
volume:5 disk:Inconsistent
peer: Connecting

On the second machine, it shows:

grobi role:Secondary
volume:2 disk:UpToDate
peer role:Primary

volume:2 replication:Established peer-disk:UpToDate

hastig role:Primary

volume:1 disk:UpToDate
volume:3 disk:UpToDate
volume:4 disk:UpToDate

volume:5 disk:UpToDate

Any idea what is going on and what I can do now to make RAID hastig
work? The two machines are in the same network and I have disabled all
local ip filter rules, so I do not know what might be blocking the
connection between the two servers ...

Regards
Christoph

Re: drbd raid stays at state peer: Connecting [ In reply to ]

gianni.milo22 at gmail

Oct 17, 2021, 3:21 AM

Post #2 of 3 (510 views)

Permalink

I doubt there's something blocking the resource "hastig" as I assume the
resource was working fine in the past on both nodes? Disabling firewall on
both nodes temporarily would rule out that possibility.Most likely you are
facing some kind of network congestion on the replication network.

Does "drbdadm disconnect hastig" followed by "drbdadm adjust hastig" make a
difference? Otherwise you may need to check the syslog for further clues. I
noticed that you have 4 volumes in that resource. Is there a specific need
to have them configured on one resource rather than creating a separate
resource for each ? I'm not saying it's wrong, it's kind of unusual...

On Sun, 17 Oct 2021 at 10:07, Christoph Pleger <
Christoph.Pleger@cs.tu-dortmund.de> wrote:

> Hello,
>
> on two servers, I created two drbd resources, where one server is the
> primary for the first resource and the other server is the primary for
> the second resource. A dump of my setup is attached.
>
> Unfortunately, the drbd RAID works for the first resource, but it does
> not for the second. "drbdadm status" since almost two days now shows on
> the first machine:
>
> grobi role:Primary
> volume:2 disk:UpToDate
> peer role:Secondary
>
> volume:2 replication:Established peer-disk:UpToDate
>
> hastig
> role:Secondary
> volume:1 disk:Inconsistent
> volume:3 disk:Inconsistent
>
> volume:4 disk:Inconsistent
> volume:5 disk:Inconsistent
> peer: Connecting
>
> On the second machine, it shows:
>
> grobi role:Secondary
> volume:2 disk:UpToDate
> peer role:Primary
>
> volume:2 replication:Established peer-disk:UpToDate
>
> hastig role:Primary
>
> volume:1 disk:UpToDate
> volume:3 disk:UpToDate
> volume:4 disk:UpToDate
>
> volume:5 disk:UpToDate
>
>
> Any idea what is going on and what I can do now to make RAID hastig
> work? The two machines are in the same network and I have disabled all
> local ip filter rules, so I do not know what might be blocking the
> connection between the two servers ...
>
> Regards
> Christoph
>
>
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT
> drbd-user mailing list
> drbd-user@lists.linbit.com
> https://lists.linbit.com/mailman/listinfo/drbd-user
>

Re: drbd raid stays at state peer: Connecting [ In reply to ]

Christoph.Pleger at cs

Oct 17, 2021, 4:07 AM

Post #3 of 3 (510 views)

Permalink

Hello,

> I doubt there's something blocking the resource "hastig" as I assume the
> resource was working fine in the past on both nodes?

The resource is new and so far has never been in sync between the two
nodes.

> Does "drbdadm disconnect hastig" followed by "drbdadm adjust hastig" make a
> difference?

Hm. Executing that on the secondary node shows:

??: Failure: (162) Invalid configuration request
additional info from
kernel:
unknown connection
Command 'drbdsetup-84 disconnect
ipv4:129.217.5.61:7790 ipv4:129.217.5.62:7790' terminated with exit
code 10

On the other host the same output, only with ip addresses the other way
round.

Regards
Christoph

_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
https://lists.linbit.com/mailman/listinfo/drbd-user

Mailing List Archive

Mailing List Archive

Attached Files: