Solaris Vol. Mgr. Question
I have a Solaris 10 server with two internal disk drives. The drives are c0t0d0 and c0t1d0. Yesterday, c0t1d0 (mirrored drive) died and I had it replaced.
Below is the metadb -i output from the failure
--
flagsfirst blkblock count
a m p lu 16 8192/dev/dsk/c0t0d0s7
ap l 82088192/dev/dsk/c0t0d0s7
M Wp l o16 unknown /dev/dsk/c0t1d0s7
M Wp l o8208unknown /dev/dsk/c0t1d0s7
Below is the metadb -i output after the disk replacement and running the appropriate meta commands
-
flagsfirst blkblock count
a m p luo16 8192/dev/dsk/c0t0d0s7
ap luo82088192/dev/dsk/c0t0d0s7
au 16 8192/dev/dsk/c0t1d0s7
au 82088192/dev/dsk/c0t1d0s7
When the drive was replaced I had run the following
========================================
prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/c0t1d0s2
metadb -a -c 2 c0t1d0s7
metareplace -e d4 c0t1d0s5
metareplace -e d3 c0t1d0s4
metareplace -e d2 c0t1d0s3
metareplace -e d1 c0t1d0s1
metareplace -e d0 c0t1d0s0
I watched the disks resync and the metastat command returns no errors.
My problem is this, when the drive initially died, iostat -En was showing 58 hard errors. After running the above procedures on the new drive, iostat -En is showing 71 hard errors on the new drive. Additionally, when going into the format menu and selecting on the new drive, I see the following messages:
selecting c0t1d0
[disk formatted]
/dev/dsk/c0t1d0s0 is part of SVM volume stripe:d11. Please see metaclear(1M).
/dev/dsk/c0t1d0s1 is part of SVM volume stripe:d22. Please see metaclear(1M).
/dev/dsk/c0t1d0s3 is part of SVM volume stripe:d33. Please see metaclear(1M).
/dev/dsk/c0t1d0s4 is part of SVM volume stripe:d44. Please see metaclear(1M).
/dev/dsk/c0t1d0s5 is part of SVM volume stripe:d55. Please see metaclear(1M).
/dev/dsk/c0t1d0s7 contains an SVM mdb. Please see metadb(1M).
I am somewhat of a newby to Solaris Volume Manager and I want to make sure that I don't corrupt any of my data. I read in another post on this forum that the metaclear messages mentioned above were just warnings and nothing to be concerned about, however, seeing 71 hard errors on the new drive obviously has me concerned.
Any input or assistance on this would be greatly appreciated.
