The recommended actions for these alerts guide you in correcting the situation.
Bad blocks are cleared by deallocating the volume disk extent by deleting the
volume or by issuing write I/O to the block. It is good practice to correct bad
blocks as soon as they are detected. This action prevents the bad block from being
propagated when the volume is replicated or migrated. It is possible, however, for
the bad block to be on part of the volume that is not used by the application. For
example, it can be in part of a database that has not been initialized. These bad
blocks are corrected when the application writes data to these areas. Before the
correction happens, the bad block records continue to use up the available bad
block space.
28
Storwize V7000: Troubleshooting, Recovery, and Maintenance Guide
|
|
|
|
|
|
|
|
|
|
Содержание Storwize V7000
Страница 1: ...IBM Storwize V7000 Version 6 3 0 Troubleshooting Recovery and Maintenance Guide GC27 2291 02...
Страница 6: ...vi Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 8: ...viii Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 10: ...x Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 34: ...18 Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 42: ...26 Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 80: ...64 Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 128: ...112 Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 156: ...140 Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 166: ...150 Storwize V7000 Troubleshooting Recovery and Maintenance Guide...
Страница 171: ......
Страница 172: ...Printed in USA GC27 2291 02...