Okay, I think I have some new information on this problem. First, upgrading to drbd 8.4.2 did not help.
I believe the problem is that when I do 'crm node offline' Pacemaker is fully stopping the drbd service. This causes drbd on the secondary to go into a "WFConnection" state. It refuses to promote to primary in that state. To figure this out, I did this... On the primary: crm node standby cat /proc/drbd (repeatedly until I saw that drbd was unloaded) /etc/init.d/drbd start (quickly before Pacemaker in the secondary tried to promote the drbd resource) drbd started and wend into a secondary.secondary state Failover succeeded and the secondary became the new primary. Is Pacemaker supposed to be fully shutting down the drbd service when you do 'crm node standby'? That seems to be what is causing the problem. -- Eric Robinson Disclaimer - December 5, 2012 This email and any files transmitted with it are confidential and intended solely for General Linux-HA mailing list. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
