From: Tom Jones (tjones@statesman.com)
Date: Tue Aug 03 2004 - 19:23:13 EDT
Configuration: E4000 HA pair running Solaris 2.6, Disksuite 4.1,
HA 1.3, 2xSSA214, 1xSSA114.
Problem: The SSA114 keeps going online and offline. The array doesn't have
any data on it, just metadb replicas for the HA 1.3. I have a service
call in with Sun to replace the FCOMs but have had problems in the
past trying to replace the array controller and FCOMs.
The 3 arrays were originally configured for HA 1.2 which
had a requirement for 3 arrays to distribute the metadbs.
HA 1.3 dropped the requirement for 3 arrays.
I'd like to delete the metadb replicas on the SSA114 but don't
want to jeopardize the HA 1.3 cluster.
Here's the metadb -i output for one node of the cluster:
=========================================================
flags first blk block count
a m luo 16 1034 /dev/dsk/c0t0d1s7
a luo 16 1034 /dev/dsk/c0t0d3s7
a luo 16 1034 /dev/dsk/c2t0d4s7
a luo 16 1034 /dev/dsk/c3t0d0s7
a luo 16 1034 /dev/dsk/c3t3d0s7
a luo 16 1034 /dev/dsk/c2t0d3s7
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/opt/SUNWmd/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
I want to delete the replicas on c3.
Am I safe deleting them under HA 1.3? Has anyone else experienced this problem?
Thanks
Tom Jones
_______________________________________________
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:29:12 EDT