Critical IO Errors: Difference between revisions

From Scalelogic Wiki
Jump to navigation Jump to search
m 1 revision
No edit summary
Line 3: Line 3:
The reboot procedure may be done by two options :
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.
*'''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.


*'''automatically''' - System will restart in 30 seconds from when the errors appear.
*'''automatically''' - System will restart in 30 seconds from when the errors appear.

Revision as of 09:49, 12 March 2020

If a Genesis NX2 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.
  • automatically - System will restart in 30 seconds from when the errors appear.
  • manually - System will prompt for manual restart.