- 论坛徽章:
- 0
|
v880上做raid 出现的问题
我顺便查了下文档
Maintenance vs. Last Erred States
When a slice in a mirror or RAID5 metadevice device experiences errors, DiskSuite
puts the slice in the “Maintenance” state. No further reads or writes are performed to
a slice in the “Maintenance” state. Subsequent errors on other slices in the same
metadevice are handled differently, depending on the type of metadevice. 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. With a slice in the “Last Erred” state, the metadevice behaves like a
normal device (disk) and returns I/O errors to an application. Usually, at this point
some data has been lost.
Always replace slices in the “Maintenance” state first, followed by those in the “Last
Erred” state. After a slice is replaced and resynced, use the metastat(1M)
command to verify its state, then validate the data to make sure it is good. |
|