Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Ben, It looks like you could be seeing a split brain operation from heartbeat. That is where both nodes think they own something. Pulling the network cable isn't the best approach to doing the testing. Rather, instead of pulling the cables, gracefully shutdown heartbeat on the primary node and see if it fails over fine. Watch the secondary node at the same time and see if the resources are being owned properly. Then you can do some more destructive tests like maybe pulling the power code (not recommended for production environments but we do this as part of our testing in dev). You should also post your ha.cf, haresources and your network config files so we can try to help out on those. Everything else is just guesswork on my part. Gary Wayne Smith > -----Original Message----- > From: Ben [mailto:bench at silentmedia.com] > Sent: Sunday, March 26, 2006 12:48 PM > To: Gary W. Smith > Cc: drbd-user at lists.linbit.com > Subject: Re: [DRBD-user] newbie drbd/HA configuration question > > Thanks! That's exactly what I needed to know. So, my next question > is, after doing this, pulling the network cable out and watching > heartbeat perform as desired, plugging the network cable back in and > watching heartbeat perform as desired, I see that things didn't quite > return to normal. > > One node sees a DRBD disk in Primary/Unknown, and the other sees the > disk in Secondary/Unknown. I'm able to use the disk just fine on the > primary, but why isn't each node able to see the state of the other > node? And should I be worried? >