Critical IO Errors: Difference between revisions
Jump to navigation
Jump to search
migrate>To-K No edit summary |
migrate>To-K No edit summary |
||
| Line 3: | Line 3: | ||
<span style="font-family: arial;">The reboot procedure may be done by two options :</span> | <span style="font-family: arial;">The reboot procedure may be done by two options :</span> | ||
*'''<span style="font-family: arial;"> | *'''<span style="font-family: arial;">Immediate</span>'''<span style="font-family: arial;">- </span>System will reboot the machine immediately after a pool has I/O suspended state. No event will be recorded about the reason of it. This option is recommended for cluster configurations because it immediately triggers the failover and therefore it`s the fastest way to restore the access to the data. | ||
*'''<span style="font-family: arial;"> | *'''<span style="font-family: arial;">automatically </span>'''<span style="font-family: arial;">- </span>System will restart in 30 seconds from when the errors appear. | ||
*'''<span style="font-family: arial;">manually - </span>'''System will prompt for manual restart. | |||
Revision as of 10:51, 28 August 2015
If a GenesisZX will meet the hardware errors, then a reboot will be needed.
The reboot procedure may be done by two options :
- Immediate- System will reboot the machine immediately after a pool has I/O suspended state. No event will be recorded about the reason of it. This option is recommended for cluster configurations because it immediately triggers the failover and therefore it`s the fastest way to restore the access to the data.
- automatically - System will restart in 30 seconds from when the errors appear.
- manually - System will prompt for manual restart.