Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
When I try it, it does not connect. [root at retv3130 ~]# drbdadm adjust all Command 'drbdsetup connect drbd0 ipv4:10.170.1.221:7789 ipv4:10.170.1.222:7789 --after-sb-2pri=discard-younger-primary --after-sb-1pri=discard-secondary --after-sb-0pri=discard-younger-primary --protocol=B' terminated with exit code 20 [root at retv3131 ~]# drbdadm adjust all Command 'drbdsetup connect drbd0 ipv4:10.170.1.222:7789 ipv4:10.170.1.221:7789 --after-sb-2pri=discard-younger-primary --after-sb-1pri=discard-secondary --after-sb-0pri=discard-younger-primary --protocol=B' terminated with exit code 20 And there is nothing new in the event logs for the last two hours except some messages from NTP. Scot Kreienkamp Senior Systems Engineer skreien at la-z-boy.com Right. So, if you now, while those IPs are present, do "drbdadm adjust all", does it connect and sync up? Or at least produce additional kernel logs? -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.