Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I think I got it, and for the forum, here's what I did. I'm guessing that somehow I wound up with a split brain condition within DRBD. Though I could influence the cs state by starting drbd on each node in a different order (which led me to conclude they WERE talking, just refusing to connect), they would not complete the connection. I found on the man page for drbdsetup, under the NET command, the option -D, and the key phrase "nodes refuse to connect" ;) The command I used was: drbdsetup /dev/drbd0 NET 10.4.4.5 10.4.4.4 C -D The partitions are now connected and resyncing. Doug On Fri, 2007-05-04 at 15:43 +0200, Lars Ellenberg wrote: > On Fri, May 04, 2007 at 09:32:30AM -0400, Doug Knight wrote: > > Does anyone know what could cause the two drbd processes to not connect? I > > managed to get a reboot in on the other server, and still they are not > > connecting and synching. The drbd mirrored pair has been down almost 16 hours > > now. > > there should be something in your kernel logs... > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20070504/57b39b5c/attachment.htm>