From: Erek Adams (erek@theadamsfamily.net)
Date: Wed Jan 04 2006 - 18:30:06 EST
NodeA-v890
NodeB-v890
Shared-3510 AC
SunCluster 3.1
We lost power to the cluster--Don't ask, to ugly to tell... Before then
everything was fine. Now, I get this weird problem. Bring up array,
comes up fine. Bring up node1, boots, and starts to grab the array.
Pauses a while then starts giving the following error:
Jan 4 16:22:41 node1 Cluster.Framework: stderr: metaset:
node1: ingdg: not owner of metadevice database
Jan 4 16:22:41 node1 Cluster.Framework: stderr: metaset:
node1: ingdg: must be owner of the set for this command
Over and over....
I've tried: pulling the heartbeats and booting only node1. It just
flips the above messages over and over. If I try to boot node2, node2
hangs on boot waiting on node1. I've killed the heartbeat between the two
boxes, with no luck. I can boot node1 in non-cluster mode and I get the
same error.
>From what I've found, it seems that purging the metadb and then recreating
it. I'm hoping that's not the fix... It just sounds
unpleasant.
Thoughts, ideas, suggestions?
-----
Erek Adams
Nifty-Type-Guy
TheAdamsFamily.Net
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:38:21 EDT