From: Chris Purcell (sunmanagers@cjp.us)
Date: Tue Oct 11 2005 - 11:08:35 EDT
I have a Solaris 6 server where the disks used in each metadevice does not
correspond to the real disk numbers. For example, most of the disks that
are part of metadevices start with c2tXdXsX, while the actual disk names
in the system are c1tXdXsX. I believe this was caused by a hardware
change that probably happened somewhere along the line. The metadevices
still work somehow, but I'm not sure why or how they still work. I
found out about this when one of the devices needed maintenance and I ran
the metareplace command....
bash-2.05# metareplace -e d1 c2t5d0s3
metareplace: earthquake: c2t5d0s3: No such file or directory
The new disk name would be c1t5d0s3. I need to fix all of these for each
metadevice. Here's an example of one...
d1: RAID
State: Needs Maintenance
Invoke: metareplace d1 c2t5d0s3 <new device>
Interlace: 64 blocks
Size: 100615336 blocks
Original device:
Size: 100617984 blocks
Device Start Block Dbase State Hot Spare
c2t5d0s3 5362 No Maintenance
c2t5d1s3 5362 No Okay
c2t5d3s3 5362 No Okay
c2t5d4s3 5362 No Okay
What is the best way to fix these metadevices? I don't think that the
server will come back up after a reboot in its current state.
How are these devices still working when they are referencing disk names
that do not exist anymore?
What, besides a defective disk, causes metadevices to require maintenance?
This happens often, and a lot of times simply running the metareplace
command fixes the situation.
fyi, the uptime on this server is over 600+ days!!
Thanks for the help!
_______________________________________________
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:32:46 EDT