Loading...
Loading...
When a cluster has a device (drive or node) that is failed or is smartfailing, the cluster is considered to be running in a degraded mode. In degraded mode, a FlexProtect or FlexprotectLIN is run to restripe and reprotect the data that was on the failed device. The Job Engine prevents other restripe jobs from running until the FlexProtect or FlexprotectLIN job is complete. A restripe job is a job that handles file system management, data protection, and on-disk layout. That includes the following jobs: AutoBalance AutoBalanceLin FlexProtect FlexProtectLin MediaScan MultiScan SetProtectPlus ShadowStoreProtect SmartPools Upgrade
The data protection feature of OneFS prevents other restripe operations from being performed while FlexProtect performs necessary protection operations. This protection preserves data integrity and minimizes risk to data. This article provides a way to temporarily disable this protection feature. This should only be done when jobs such as autobalance or SmartPools must run to address immediate node balance or disk space issues.
Caution: This change should only be applied if there is a compelling and immediate reason to do so. The change should remain only as needed and must be reverted when done. Failure to restore the run_degraded setting to false may cause future job failure or job performance issues. Allow jobs other than FlexProtect to run during a degraded state. Open an SSH connection on any node in the cluster and log in using the "root" account. Run the following command to enable run_degraded mode: isi_gconfig -t job-config core.run_degraded=true Other jobs should now be able to run. After the situation is resolved that required running other jobs, revert the change to disable run_degraded. Restore to normal default, exclusion of restripe jobs. Open an SSH connection on any node in the cluster and log in using the "root" account. Run the following command to disable run_degraded mode (default): isi_gconfig -t job-config core.run_degraded=false Verify that the default settings have been correctly restored by running the following command: isi_gconfig -t job-config core.run_degraded The output should return false.
Click on a version to see all relevant bugs