The thin volume's repository is over the threshold value.
What Caused the Problem?
A thin volume's repository capacity has exceeded the warning threshold level. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
If you do not resolve this problem, this is the last warning you will receive before the thin volume's repository becomes full.
If the thin volume's repository capacity becomes full, it will not have enough capacity to save new data. Therefore, the thin volume will continue to fail write requests that require repository capacity.
The thin volume's repository expansion policy determines the method by which the repository will be expanded as capacity is used. To determine the expansion policy, highlight the thin volume and select the
Storage > Volume > Change > Repository Settings
menu option.
If the expansion policy is set to automatic (recommended), the repository will automatically expand as capacity is used in order to avoid a repository full problem. You can specify a maximum expansion capacity, which is the limit to how large the repository can grow before it no longer expands automatically.
If the expansion policy is set to manual, you will need to expand the repository manually as capacity is used.
To resolve this problem, increase the repository's maximum expansion capacity (automatic policy only), or modify the threshold capacity warning level (automatic and manual policies). Note that increasing the warning threshold will reduce the time you have to respond the next time you receive a threshold notification. If the warning threshold is disabled, you will only receive notification when the repository is full.
Recovery Steps
1 |
| ||||||||||||||||||||||||||
2 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your Technical Support Representative. |
| Target | NetAppESeries.StorageArray | ||
| Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0429_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_TPV_REPOSITORY_OVER_THRESHOLD_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="NetAppESeries.StateIdD40E96A0CD922A86CB22E93C3D5120F6" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId42AC7648FA60CF1FC1A9F10329BA84E" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>429</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>