Critical IO Errors: Difference between revisions

From Scalelogic Wiki
Jump to navigation Jump to search
migrate>To-K
No edit summary
m 1 revision
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
If a GenesisZX will meet the hardware errors, then a reboot will be needed. 
#REDIRECT [[Critical system error response policy]]
 
<span style="font-family: arial;">The reboot procedure may be done by two options&nbsp;:</span>
 
*'''<span style="font-family: arial;">Immediate</span>'''<span style="font-family: arial;">-&nbsp;</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;">automatically&nbsp;</span>'''<span style="font-family: arial;">-&nbsp;</span>System will restart in 30 seconds from when the errors appear.
 
*'''<span style="font-family: arial;">manually -&nbsp;</span>'''System will prompt for manual restart.

Latest revision as of 11:40, 21 January 2025