From: Ray Pasetes (rayp@fnal.gov)
Date: Mon Nov 24 2003 - 09:38:00 EST
Hi,
We have a Sun 280R, Solaris9, Veriatas VM 3.5. We are using VxVM to
mirror the two internal FC disks. One of our disks went bad and we have
since replaced it. The OS can see the new disk (verified by format,
newfs, mounting) but when we do a vxdisk print, we see that the device,
c1t1d0 is in error. vxdiskadm can not use it to replace the failed
mirror because it thinks c1t1d0 is offline. In short, somewhere in
veritas land, it still has the old device path name to c1t1d0 (belonging
to the bad disk) even though the OS has already changed the c1t1d0 link
in /dev to the new disk device.
The 280R, using FC disks, has the WWN in the long device path name,
i.e. /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cfb4f67c,0 (ssd0),
and it seems that vxvm has mapped this internally somewhere. How do
we tell vxdm that c1t1d0's real device has changed? We've tried
vxdctl enable, playing with devfsadm, luxadm no help. We tried
vxdiskadm to remove c1t1d0 and re-add c1t1d0 and vxvm still complains
that c1t1d0 is offline, but it is not.
Thanks for any help/advice.
-- ============================================== Ray Pasetes Email: rayp@fnal.gov CD/CSS/CSI Phone: 630-840-5250 Fermilab, Batavia, IL Fax : 630-840-6345 ============================================== _______________________________________________ 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:27:32 EDT