- 论坛徽章:
- 0
|
v880上做raid 出现的问题
|
我顺便查了下文档 \r\n\r\nMaintenance vs. Last Erred States\r\nWhen a slice in a mirror or RAID5 metadevice device experiences errors, DiskSuite\r\nputs the slice in the “Maintenance” state. No further reads or writes are performed to\r\na slice in the “Maintenance” state. Subsequent errors on other slices in the same\r\nmetadevice are handled differently, depending on the type of metadevice. A mirror\r\nmay be able to tolerate many slices in the “Maintenance” state and still be read from\r\nand written to. A RAID5 metadevice, by definition, can only tolerate a single slice in\r\nthe “Maintenance” state. When either a mirror or RAID5 metadevice has a slice in\r\nthe “Last Erred” state, I/O is still attempted to the slice marked “Last Erred.” This is\r\nbecause a “Last Erred” slice contains the last good copy of data from DiskSuite’s\r\npoint of view. With a slice in the “Last Erred” state, the metadevice behaves like a\r\nnormal device (disk) and returns I/O errors to an application. Usually, at this point\r\nsome data has been lost.\r\nAlways replace slices in the “Maintenance” state first, followed by those in the “Last\r\nErred” state. After a slice is replaced and resynced, use the metastat(1M)\r\ncommand to verify its state, then validate the data to make sure it is good. |
|
免费注册
发表于 2005-07-02 16:40
