LINBIT DRBD (old-stable). Contribute to LINBIT/drbd development by creating an account on GitHub. You don’t want to create the filesystem on your backing disks for DRBD (sdb and sdc); you want to create the DRBD first, and then format the. Drbdadm is the high level tool of the DRBD program suite. Drbdadm is to drbdsetup and drbdmeta what ifup/ifdown is to ifconfig. Drbdadm.
|Published (Last):||12 January 2009|
|PDF File Size:||19.92 Mb|
|ePub File Size:||19.27 Mb|
|Price:||Free* [*Free Regsitration Required]|
It’s not an issue of the “right order”, it’s that you’re writing stuff to a device which does or will underly DRBD other than to clear it in advance as suggested in this answer. Sign up using Facebook.
drbdadm(8) — drbd-utils — Debian stretch — Debian Manpages
I know the reason. I have did what you suggest: Device ‘0’ is configured!
I was using basic 10GB disk on each node. Sign up using Email and Password.
centos7 – Can’t run drbdadm up with DRBD on CentOS – Server Fault
Email Drdb, but never shown. The process should be something like this: And ran lsblk -a now: After I added the new hard disk on both nodes, I did partition and format on them!
After run that zero out command, both of showed: Added 16GB new hard disk on each node. Sign up or log in Sign up using Google.
drbd.conf-8.4 man page
Thank you very much for your very good answer! It’s the right order.
Wait for a long time returned no result. The only necessary thing is do the partition only. Erbd I ran your commands, the result was the same.
Don’t do drbx, you don’t know what you’re doing: DRBD is obviously a great tool, and is easy to use once you understand the basics, but you’re dealing with storage so there is a lot of room to mess things up in a permanent way.
It can be done the other way, but then you’d need to grow the backing partition, or reduce the size of the filesystem to make room for DRBD’s metadata which lives at the end of the block device when using internal metadata.