This post is because while patching a Solaris 10 server with patch level Generic_142900-02 to Generic_142900-13.. There’s a need maintenance error on one of the sub mirror:<\/p>\n
When a slice in a mirror or RAID5 metadevice device experiences errors,
\nDiskSuite puts the slice in the “Maintenance” state. No further reads or
\nwrites are performed to a slice in the “Maintenance” state. Subsequent
\nerrors on other slices in the same metadevice are handled differently,
\ndepending on the type of the metadevice.<\/p>\n
A mirror may be able to tolerate many slices in the “Maintenance” state and still be read from and written to. A RAID5 metadevice, by definition, can only tolerate a single slice in the “Maintenance” state. When either a mirror or RAID5 metadevice has a slice in the “Last Erred” state, I\/O is still attempted to the slice marked “Last Erred”. This is because a “Last Erred” slice contains the last good copy of data from DiskSuite’s point of view.<\/p>\n
\nWith a slice in the “Last Erred” state, metadevice behaves like a normal
\ndevice (disk) and returns I\/O errors to an application. Usually, at this
\npoint some data has been lost.
\nAlways replace slices in the “Maintenance” state, followed by those in the
\n“Last Erred” state. After a slice is replaced and resynched, use the metastat
\ncommand to verify its state, then validate data to make sure it is good.
\nHere are the specifics for Mirrors and RAID5 devices:
\n1. Mirrors
\nIf slices are in the “Maintenance” state, no data has been lost. You can
\nsafely replace or enable the slices in any order. If a slice is in the “Last
\nErred” state, you cannot replace it until you first replace all the other
\nmirrored slices in the “Maintenance” state. Replacing or enabling a slice in
\nthe “Last Erred” state usually means that some data has been lost. Be sure
\nto validate the data on the mirror after repairing it.
\n2. RAID5 metadevices
\nA RAID5 metadevice can tolerate a single slice failure. You can safely
\nreplace a single slice in the “Maintenance” state without losing data. If
\nan error on another slice occurs, it is put into the “Last Erred” state. At
\nthis point, the RAID5 metadevice is a read-only device; you need to perform
\nsome type of error recovery so that the state of the RAID5 metadevice is
\nnon-errored and the possibility of data loss is reduced. If a RAID5
\nmetadevice reaches a “Last Erred” state, there is a good chance it has
\nlost data. Be sure to validate the data on the RAID5 metadevice after
\nrepairing it.
\nHow to remove “maintenance” and “last erred” example, In this point maybe pay attention
\nin some case The “lost Erred” sub-mirror side have contained “maintenance” and “Okey” state<\/p>\n
Metastat gives :
\nd0: Mirror
\nSubmirror 0: d10
\nState: Needs maintenance
\nSubmirror 1: d20
\nState: Needs maintenance
\nPass: 1
\nRead option: roundrobin (default)
\nWrite option: parallel (default)
\nSize: 8395200 blocksd10: Submirror of d0
\nState: Needs maintenance
\nInvoke: after replacing “Maintenance” components:
\nmetareplace d0 c1t0d0s0
\nSize: 8395200 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t0d0s0 0 No Last Erred
\nd20: Submirror of d0
\nState: Needs maintenance
\nInvoke: metareplace d0 c1t1d0s0
\nSize: 8395200 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t1d0s0 0 No Maintenance
\nd1: Mirror
\nSubmirror 0: d11
\nState: Okay
\nSubmirror 1: d21
\nState: Okay
\nPass: 1
\nRead option: roundrobin (default)
\nWrite option: parallel (default)
\nSize: 8395200 blocksd11: Submirror of d1
\nState: Okay
\nSize: 8395200 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t0d0s1 0 No Okay
\nd21: Submirror of d1
\nState: Okay
\nSize: 8395200 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t1d0s1 0 No Okay
\nd4: Mirror
\nSubmirror 0: d14
\nState: Needs maintenance
\nSubmirror 1: d24
\nState: Needs maintenance
\nPass: 1
\nRead option: roundrobin (default)
\nWrite option: parallel (default)
\nSize: 4202688 blocksd14: Submirror of d4
\nState: Needs maintenance
\nInvoke: after replacing “Maintenance” components:
\nmetareplace d4 c1t0d0s4
\nSize: 4202688 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t0d0s4 0 No Last Erred
\nd24: Submirror of d4
\nState: Needs maintenance
\nInvoke: metareplace d4 c1t1d0s4
\nSize: 4202688 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t1d0s4 0 No Maintenance
\nd5: Mirror
\nSubmirror 0: d15
\nState: Okay
\nSubmirror 1: d25
\nState: Okay
\nPass: 1
\nRead option: roundrobin (default)
\nWrite option: parallel (default)
\nSize: 62918208 blocksd15: Submirror of d5
\nState: Okay
\nSize: 62918208 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t0d0s5 0 No Okay
\nd25: Submirror of d5
\nState: Okay
\nSize: 62918208 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t1d0s5 0 No Okay
\nd6: Mirror
\nSubmirror 0: d16
\nState: Needs maintenance
\nSubmirror 1: d26
\nState: Okay
\nPass: 1
\nRead option: roundrobin (default)
\nWrite option: parallel (default)
\nSize: 52436928 blocksd16: Submirror of d6
\nState: Needs maintenance
\nInvoke: metareplace d6 c1t0d0s6
\nSize: 52436928 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t0d0s6 0 No Maintenance
\nd26: Submirror of d6
\nState: Okay
\nSize: 52436928 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t1d0s6 0 No Okay
\nd7: Mirror
\nSubmirror 0: d17
\nState: Okay
\nSubmirror 1: d27
\nState: Needs maintenance
\nPass: 1
\nRead option: roundrobin (default)
\nWrite option: parallel (default)
\nSize: 6970560 blocksd17: Submirror of d7
\nState: Okay
\nSize: 6970560 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t0d0s7 0 No Okay
\nd27: Submirror of d7
\nState: Needs maintenance
\nInvoke: metareplace d7 c1t1d0s7
\nSize: 6970560 blocks
\nStripe 0:
\nDevice Start Block Dbase State Hot Spare
\nc1t1d0s7 0 No Maintenance
\n-First dettach,delete master slice6 and resync with mirror side slice6,Because in this way the intact data only in mirror side:
\n# metadetach d6 d16
\n# metaclear d16
\n# metainit d16 1 1 c1t0d0s6
\n# metattach d6 d16
\n– Wait for “Okay” status for the master slice6,
\n– Then replace “Last erred” state disk before.
\nRun “metadetach” to detach all the sub-mirrors on the mirror disk from
\ntheir respective mirrors (see the following):
\n[b]# metadetach -f [\/b]
\nNOTE: The “-f” option is not required if the metadevice is in an “okay”
\nstate.
\nThen run metaclear to remove the configuration from the disk:
\n[b]# metaclear [\/b]
\n# metadb -d c1t1d0s3
\n# luxadm remove_device \/dev\/rdsk\/c1t1d0s2 (physical remove disk when prompt to pull out disk)
\n# devfsadm -C -c disk -v
\n# luxadm insert_device \/dev\/rdsk\/c1t1d0s2 (physical insert disk when prompt to pull in disk)
\n# prtvtoc \/dev\/rdsk\/c1t0d0s2 |fmthard -s – \/dev\/rdsk\/c1t1d0s2
\n# metadb -afc 3 c1t1d0s3
\nUse “metainit” and “metattach” to re-create and attach those submirrors to
\nthe mirrors to start the resync:
\n[b]# metainit 1 1 c#t#d#s#[\/b]
\n[b]# metattach [\/b]
\nWhen all slice resync are finished,Begin replace “Last Erred” master disk
\nRun “metadetach” to detach all the sub-mirrors on the master disk from
\ntheir respective mirrors (see the following):
\n[b]# metadetach -f [\/b]
\nNOTE: The “-f” option is not required if the metadevice is in an “okay”
\nstate.
\nThen run metaclear to remove the configuration from the disk:
\n[b]# metaclear [\/b]
\n# metadb -d c1t1d0s3
\n# luxadm remove_device \/dev\/rdsk\/c1t0d0s2 (physical remove disk when prompt to pull out disk)
\n# devfsadm -C -c disk -v
\n# luxadm insert_device \/dev\/rdsk\/c1t0d0s2 (physical insert disk when prompt to pull in disk)
\n# prtvtoc \/dev\/rdsk\/c1t1d0s2 |fmthard -s – \/dev\/rdsk\/c1t0d0s2
\n# metadb -afc 3 c1t0d0s3
\nUse “metainit” and “metattach” to re-create and attach those submirrors to
\nthe mirrors to start the resync:
\n[b]# metainit 1 1 c#t#d#s#[\/b]
\n[b]# metattach [\/b]
\nWhen all slice resync finished,the two sub-mirror is normal.<\/p>\n","protected":false},"excerpt":{"rendered":"
This post is because while patching a Solaris 10 server with patch level Generic_142900-02 to Generic_142900-13.. There’s a need maintenance error on one of the sub mirror: When a slice in a mirror or RAID5 …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[347,349,350,351,379,352,111],"class_list":["post-227","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-kernel-patch","tag-mirror-disk","tag-needs-maintenance","tag-patch","tag-solaris-10","tag-solaris-patch","tag-svm"],"_links":{"self":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/227","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/comments?post=227"}],"version-history":[{"count":2,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/227\/revisions"}],"predecessor-version":[{"id":229,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/posts\/227\/revisions\/229"}],"wp:attachment":[{"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/media?parent=227"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/categories?post=227"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sysadmindayph.com\/blog\/wp-json\/wp\/v2\/tags?post=227"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}