Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Under 8.2.6 we have used a script to switch from one mirror host to another creating a new drbd.conf file under a different name, using it, and if all of the other parts of the procedure go well, making it the permanent drbd.conf file. (Otherwise we roll back using the old one). We’re switching while disconnected and change resource names that refer to our /dev/drbd devices, nodenames, ipaddresses. The underlying /dev/sda partitions and meta data partitions always continue to map to the same drbd devices. We’ve changed to 8.2.7 and now drbdadm is giving us a warning like: Warning: resource monoblock_1 last used config file: /var/opt/foo/etc/drbd.conf.tmp current config file: /etc/drbd.conf Do you want to proceed and register the current config file? *** confirmation forced via --force option *** My question is, have we been in danger all along? What exactly is this trying to protect me from? -- View this message in context: http://www.nabble.com/drbdadm---force-option-when-using-different-drbd.conf-file-tp22609667p22609667.html Sent from the DRBD - User mailing list archive at Nabble.com.