Write-back caching for one or more volumes has been forcibly disabled by the storage array.
What Caused the Problem?
Write-back caching was disabled on one or more storage pools. This problem can occur for the following reasons:
A battery has failed
There are different sizes of total installed cache memory
Cache was reconfigured
A Cache data-restore operation is in progress, which interrupted the normal write-back caching process
The space in the cache backup device is insufficient for storing the cache
The Recovery Guru Details area provides specific information about the problem.
Additional Information about the Problem
When write-back caching is enabled when storage pools are configured, write-back caching improves I/O performance. When write-back caching is disabled, I/O performance to the volume or storage pool is seriously degraded.
The error triggers a critical event.
All volumes in the storage pool may not be affected.
The controller is in the Needs Attention state.
When write-back caching is enabled, the system transitions from Needs Attention to Optimal after all storage pools configured to use write-back caching are restored.
When the system transitions from Needs Attention to Optimal, an information MEL event is logged to show that all normal write-back caching capabilities are restored for all storage pools in the system.
While in the Needs Attention state, a forced-disable of write-caching on any additional storage pools has no effect, and no state transition occurs.
The storage array will remain in a Needs Attention state until the problem is resolved.
Alerts will be sent if they have been configured.
Recovery Steps
1 | Check the Recovery Guru Summary area for other problems.
| ||||||
2 |
|
| Target | IBMStorageSubsystem.StorageSubsystem | ||
| Parent Monitor | IBMStorageSubsystem.StorageSubsystemAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | IBMStorageSubsystem.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="IBMStorageSubsystem.FailureID_0329_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="IBMStorageSubsystem.REC_WRITEBACK_CACHING_DISABLED_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="IBMStorageSubsystem.StateId335FB1B7719C094570BDE84711390EE8" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="IBMStorageSubsystem.StateId3CF192D4C68C64AB8234278CF03CA622" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>329</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>