Thank you for your answer.
The reported issue happens with drbd84 on CentOS7, details:
[root@ip-10-102-233-230 ~]# uname -r
3.10.0-862.14.4.el7.x86_64
DRBDADM_BUILDTAG=GIT-hash:\ c0fb2d367b8be5e9f53919f88a8c344dc8c61fe9\
build\ by\ mockbuild@Build64R6\,\ 2016-12-13\ 17:38:13
DRBDADM_API_VERSION=1
DRBD_KERNEL_VERSION_CODE=0x080409
DRBDADM_VERSION_CODE=0x080908
DRBDADM_VERSION=8.9.8
Once installing drbd90 I encounter problems with parsing my resource
configuration files (even though the documentation has not changed: man
drbd.conf), besides the obvious removed support for 'max-bio-bvecs' and
'unplug-watermark' the tool does not dump 'startup' section when using:
drbdadm dump "resource", however when I introduce intentional error in
section 'startup' it does complain about the syntax:
1. Intentional error:
startup {
testing;
become-primary-on ip-10-102-233-230.ec2.internal;
}
results in reported syntax:
[root@ip-10-102-233-230 ~]# drbdadm dump data0
drbd.d/data0.res:128: Parse error: '<an option keyword> | become-primary-on
| stacked-timeouts' expected,
but got 'testing'
2. Proper (?) 'startup' section:
startup {
become-primary-on ip-10-102-233-230.ec2.internal;
}
results in no 'startup' section listed on 'dump':
[root@ip-10-102-233-230 ~]# drbdadm dump data0 | grep startup
[root@ip-10-102-233-230 ~]#
Is this intentional, i.e. not to dump 'startup' section?
Details:
[root@ip-10-102-233-230 xdcluster]# drbdadm --version
DRBDADM_BUILDTAG=GIT-hash:\ fed9a1df82015e52c14c912fa4b93336e2ab4fcc\
build\ by\ mockbuild@\,\ 2018-04-20\ 19:30:46
DRBDADM_API_VERSION=2
DRBD_KERNEL_VERSION_CODE=0x09000e
DRBD_KERNEL_VERSION=9.0.14
DRBDADM_VERSION_CODE=0x090301
DRBDADM_VERSION=9.3.1
Thanks in advance,
On Wed, Oct 3, 2018 at 1:44 AM, Julien Escario <julien.esca...@altinea.fr>
wrote:
> Le 02/10/2018 à 19:56, Radoslaw Garbacz a écrit :
> > Hi,
> >
> >
> > I have a problem, which (from what I found) has been discussed, however
> not in
> > the particular case, which I experienced, so I would be grateful for any
> > suggestions of how to deal with it.
>
> Your problem sounds pretty similar to a recent experience we had BUT with
> DRBD9
> (and drbdmanage).
>
> You can try to force disconnect by firwalling ports 7789/7790 with
> iptables on
> nodes and try to force socket disconnect with
> http://killcx.sourceforge.net/.
>
> I didn't manage to get rid of this situation without rebooting a node.
>
> I was told to upgrade the drbd kernel module.
>
> Good luck !
> Julien
> _______________________________________________
> drbd-user mailing list
> drbd-user@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
--
Best Regards,
Radoslaw Garbacz
XtremeData Incorporated
_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
