Hi, If you stop the resource this is perfectly normal to get a resource diskless and unconfigured since you asked pacemaker to stop it. You just need to reconnect properly the resource 0 (guess it's the mysql one). For this, it's more or less the same operation as this one: http://www.drbd.org/users-guide-8.3/s-resolve-split-brain.html
Cheers -- Regards, Sébastien Han. On Tue, Feb 19, 2013 at 2:38 AM, Samuel Winchenbach <swinc...@gmail.com>wrote: > Hi All, > > I recently switched from CentOS 6.3 to Ubuntu LTS server and have started > encountering some really odd problems with drbd and pacemaker. everything > seems to work well until I stop a resource or migrate itl at which point > drbd either becomes "Diskless" or "Unconfigured". I am not sure what is > happening but I never had this problem in CentOS. > > pacemaker configuration: http://paste2.org/p/2905943 > drbd configuration: http://paste2.org/p/2905965 > > syslog output: http://paste2.org/p/2905988 > drbd state problems: http://paste2.org/p/2905951 > > > If someone could take a quick look at this I would be very grateful, I > have been fighting this for a couple days now. > > Thanks, > Sam > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp