Owners Manual
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
snapshot space and should be monitored. If the storage usage drops below any threshold, event
572 is logged.
Recommended actions:
● Reduce the snapshot space usage by deleting snapshots that are no longer needed.
Info. Allocated snapshot space exceeded either the low or middle snapshot space threshold.
The threshold settings are intended to indicate that the pool is using a significant portion of
configured snapshot space and should be monitored. If the storage usage drops below any
threshold, event 572 is logged.
Recommended actions:
● Reduce the snapshot space usage by deleting snapshots that are no longer needed.
572 Info. The indicated virtual pool has dropped below one of its snapshot space thresholds.
This event indicates that a condition reported by event 571 is no longer applicable.
Recommended actions:
● No action is required.
573 Warning Allocated snapshot space for a virtual pool cannot be reduced because no snapshots are
deletable.
Allocated snapshots cannot be automatically deleted if their retention priority is set to never-
delete. Snapshots must also be at the leaf end of a snapshot tree in order to be considered
deletable. This event is logged when no snapshots in the pool pass these constraints.
Recommended actions:
● Manually delete snapshots to reduce allocated snapshot space.
574 Info. A peer connection was created.
Recommended actions:
● No action is required.
575 Info. A peer connection was deleted.
Recommended actions:
● No action is required.
576 Info. A replication set was created, or a replication set failed to be created.
Recommended actions:
● No action is required.
577 Error A replication set failed to be deleted.
Recommended actions:
● No action is required.
Info. A replication set was deleted.
Recommended actions:
● No action is required.
578 Error A replication failed to start.
The replication was unsuccessful due to the condition specified within the event. Reasons for
replication failure include but are not limited to shutdown of the secondary system, a loss of
communication across the peer connection (which may be due to CHAP configuration changes),
or a pool out-of-space condition.
Events and event messages 141