It turned out that the NFS daemon was blocking DRBD.
Thanks, the comment about the 'drbd' kernel processes was helpful.
BTW, the documentation (man pages) for DRBD 9.0 is still from 8.4 and some
options are no longer there.
On Thu, Oct 11, 2018 at 9:48 AM, Radoslaw Garbacz <
Thanks, will take a closer look at this.
On Thu, Oct 11, 2018 at 3:47 AM, Lars Ellenberg
wrote:
> On Tue, Oct 02, 2018 at 12:56:38PM -0500, Radoslaw Garbacz wrote:
> > Hi,
> >
> >
> > I have a problem, which (from what I found) has been discussed, however
> not
>
DM_VERSION_CODE=0x090301
DRBDADM_VERSION=9.3.1
Thanks in advance,
On Wed, Oct 3, 2018 at 1:44 AM, Julien Escario
wrote:
> Le 02/10/2018 à 19:56, Radoslaw Garbacz a écrit :
> > Hi,
> >
> >
> > I have a problem, which (from what I found) has been discussed, howev
0.ec2.internal;
}
}
--
Best Regards,
Radoslaw Garbacz
XtremeData Incorporated
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
-> Unknown ) conn( SyncTarget -> BrokenPipe ) pdsk( UpToDate ->
DUnknown )
Apr 10 23:40:14 ip-10-10-10-133 kernel: [ 1178.423017] drbd data0: short
read (expected size 4096)
Apr 10 23:40:14 ip-10-10-10-133 kernel: [ 1178.425132] drbd data0: error
receiving RSDataReply, e: -5 l: 65536!
[...]
--
Best Regards,
Radoslaw Garbacz
XtremeData Incorporation
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
requested)
* drbdadm -d adjust
shows correctly changed settings with regard to the configured
So, is there a way for DRBD 8.4 to improve it, or is there something wrong
with the way I try to configure it.
Thanks in advance,
--
Best Regards,
Radoslaw Garbacz
XtremeData Inc
