> My guess what's happening here is this:
> Either the local node or some remote node that it can still successfully
> connect to while initializing the local DRBD was either not stopped, or
> the DRBD kernel module on it did not stop the resource successfully.
> Therefore, some node still had
51200k; # bytes/second
}
}
}
}
[root@sios0 ~]# exit
exit
Script done, file is typescript
On Thu, Jul 25, 2019 at 11:52 AM Paul Clements
wrote:
>
> Lars,
>
> Thanks for your help.
>
> > Can you post a "transscript&
Lars,
Thanks for your help.
> Can you post a "transscript"?
Attached is the typescript of the failure.
--
Paul
typescript
Description: Binary data
___
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
drbd-user@lists.linbit.com
> One thing you could check just to be sure is whether the configuration
> files are identical on all three systems.
Yes, it's identical. md5sums check out.
> Was DRBD stopped on all three nodes before you recreated the meta data?
> (Did you do 'drbdsetup down resourcename' on all three nodes,
:
>
> On 22/07/2019 20:55, Paul Clements wrote:
> > [root@sios0 ~]# drbdadm up r0
> > 0: Failure: (111) Low.dev. smaller than requested DRBD-dev. size.
> > Command 'drbdsetup attach 0 /dev/dm-0 /dev/dm-0 internal' terminated
>
> Probably a silly question and already an
Thanks for the tip. I tried it, but no luck. Did this on all three
nodes. Same output:
[root@sios0 ~]# dd if=/dev/zero of=/dev/dm-0 bs=4k
dd: error writing '/dev/dm-0': No space left on device
18358273+0 records in
18358272+0 records out
75195482112 bytes (75 GB) copied, 165.102 s, 455 MB/s
> The problem is that the new meta data for three nodes is larger than the
> old meta data for two nodes, therefore the sum of meta data and user
> data would be larger than the size of the device.
> You will have to either reduce the size of the filesystem, so that the
> new meta data fits in at
> Apparently, you used the default values when you initially created the
> DRBD meta data for this installation. Since you had only two nodes
> listed in the configuration file and did not specify otherwise, drbdadm
> created meta data for a two node cluster.
> Then you added another node to the
RHEL 7.6 with DRBD 9.0.16
I had a two-node DRBD mirror set up, but wanted to add a third node. I
redid /etc/drbd.conf as follows:
# You can find an example in /usr/share/doc/drbd.../drbd.conf.example
include "drbd.d/global_common.conf";
include "drbd.d/*.res";
resource r0 {
on sios0 {