From: prabir sarkar (prabir.kr.sarkar@gmail.com)
Date: Wed Jul 19 2006 - 10:34:03 EDT
Hi Sunmanagers,
i ran into rough weather with Suncluster
2.2running on Solaris 6. The nodes are schost1 and schost2. The
following is
the configuration of the nodes. These are Sun Enterprise 6000 servers.
SunOS schost1 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-Enterprise.
SunOS schost2 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-Enterprise.
Both schost1 and schost2 are cluster members. schost2 is primary of the
diskset "wams". There was a did device error in d2 in the wams diskset. when
i ran the following commands from the primary of the diskset (i.e from
schost2) i am asked by the system to run it from the other node (schost1)
which is NOT the current master of the diskset. please find the details
below.
root on LIVE schost2 # scdidadm -R d2
Command must be run on node 0: schost1
root on LIVE schost2 # scdidadm -r
Command must be run on node 0: schost1
i ran the commands as directed from schost1 which is NOT mastering any
diskset:-
root on LIVE schost1 # scdidadm -R 2
root on LIVE schost1 # scdidadm -r
Configuring /devices and /dev; this may take a while.
This switched the diskset from schost2 to schost1.
My query:- 1) why the scdidadm commands were not allowed to operate from the
primary of the diskset?
2) Did the diskset switch over occured as a result of CCR
reconfiguration when i ran scdidadm -r? i haven't seen a
switch over of disk device groups due to scdidadm -r
before.
Thanks in Advance.
thanks and regards
Prabir.
_______________________________________________
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:40:25 EDT