Re: [DRBD-user] drbd raid stays at state peer: Connecting
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
Re: [DRBD-user] drbd raid stays at state peer: Connecting
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.ple...@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 > ___ 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
[DRBD-user] drbd raid stays at state peer: Connecting
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
# /etc/drbd.conf
global {
usage-count yes;
cmd-timeout-medium 600;
cmd-timeout-long 0;
}
common {
net {
max-buffers 8000;
max-epoch-size 8000;
sndbuf-size0;
}
disk {
al-extents 3389;
}
handlers {
before-resync-target "/usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15
-- -c 16k";
after-resync-target /usr/lib/drbd/unsnapshot-resync-target-lvm.sh;
}
}
# resource grobi on ernie: not ignored, not stacked
# defined at /etc/drbd.d/grobi.res:1
resource grobi {
on ernie {
volume 2 {
device /dev/drbd2 minor 2;
disk /dev/vg0/game;
meta-diskinternal;
}
address ipv4 129.217.5.61:7789;
}
on bert {
volume 2 {
device /dev/drbd2 minor 2;
disk /dev/vg0/game;
meta-diskinternal;
}
address ipv4 129.217.5.62:7789;
}
}
# resource hastig on ernie: not ignored, not stacked
# defined at /etc/drbd.d/hastig.res:1
resource hastig {
on ernie {
volume 1 {
device /dev/drbd1 minor 1;
disk /dev/vg0/dhcp;
meta-diskinternal;
}
volume 3 {
device /dev/drbd3 minor 3;
disk /dev/vg0/ls4_linf;
meta-diskinternal;
}
volume 4 {
device /dev/drbd4 minor 4;
disk /dev/vg0/schlick;
meta-diskinternal;
}
volume 5 {
device /dev/drbd5 minor 5;
disk /dev/vg0/tux;
meta-diskinternal;
}
address ipv4 129.217.5.61:7790;
}
on bert {
volume 1 {
device /dev/drbd1 minor 1;
disk /dev/vg0/dhcp;
meta-diskinternal;
}
volume 3 {
device /dev/drbd3 minor 3;
disk /dev/vg0/ls4_linf;
meta-diskinternal;
}
volume 4 {
device /dev/drbd4 minor 4;
disk /dev/vg0/schlick;
meta-diskinternal;
}
volume 5 {
device /dev/drbd5 minor 5;
disk /dev/vg0/tux;
meta-diskinternal;
}
address ipv4 129.217.5.62:7790;
}
}
___
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
