ZFS Pool Capacity Critical Alert - Troubleshooting Guide
Purpose
This document provides a standardized approach for handling and troubleshooting the ZFS Pool Capacity Critical alert, enabling rapid response to prevent storage exhaustion, performance degradation, and potential service outages.
Alert Name
ZFS Pool Capacity Critical
Alert Description
This alert is triggered when ZFS pool utilization exceeds 95%, indicating that the storage pool is critically full.
At this level, the system may experience:
-
Severe performance degradation
- Increased write latency
- Risk of write failures
This condition significantly increases the risk of:
-
Pool instability
- Application/service disruption
- Potential data loss scenarios
Severity
P1- Critical Impact
Possible Causes
- Rapid data growth or unexpected spikes
- Accumulation of snapshots
- Lack of storage cleanup
- Inefficient dataset usage
- No capacity planning or monitoring
- High fragmentation impacting usable space
L1 Engineer Actions
Step 1 – Log the Alert
- Log in to the monitoring system
- Review alert summary and affected pool
Step 2 – Create Ticket
- Immediately inform L2 team (P1 priority)
- Create an internal ticket including:
- Alert name
- Hostname
- Pool name
- Current utilization (%)
- Timestamp
Step 3 – Escalation (If required)
- Ensure immediate escalation to L2
- Share all relevant details
Step 4 – Documentation
- Update Issue Master Sheet with incident details
- Ensure tracking for critical incident
L2 Engineer Actions
Step 1 – Check Pool Status & Usage
zpool list
zpool status
- Verify pool capacity and health
- Identify utilization percentage
Step 2 – Analyze Fragmentation
zpool list
- Check fragmentation levels
- Identify performance impact
- Perform urgent cleanup:
- Remove unnecessary data
- Delete unused snapshots
- If cleanup is insufficient:
- Plan for pool expansion
Step 4 – OEM Escalation
- Inform OEM/vendor for:
- Capacity expansion
- Storage planning support
Step 5 – Capacity Expansion (If required)
- Add new disks or extend pool
- Monitor pool after expansion
Resolution
The issue is considered resolved when:
-
ZFS pool utilization drops below critical threshold
- Sufficient free space is available
- No performance degradation observed
- Alert is cleared
Escalation
- L1 → L2: Immediate escalation for P1 alert
- L2 → OEM/Vendor: For storage expansion or hardware support
Related Articles
ZFS Pool Capacity Warning Alert - Troubleshooting Guide
Purpose This document provides a standardized approach for handling and troubleshooting the ZFS Pool Capacity Warning alert, helping L1 and L2 engineers prevent storage exhaustion and maintain system stability. Alert Name ZFS Pool Capacity Warning ...
ZFS Pool Error Alert - Troubleshooting Guide
Purpose This document provides a standardized approach for handling and troubleshooting the ZFS Pool Error alert, enabling L1 and L2 engineers to quickly identify disk-related issues, prevent data loss, and maintain storage reliability. Alert Name ...
Network Down Extern (P1 Critical Alert) - Troubleshooting Guide
Purpose This document provides a standardized approach for handling and troubleshooting the Network Down - Extern alert, including L1 and L2 actions, escalation procedures, and resolution criteria for critical incidents. Alert Name Network Down - ...
Network Down Boot (P1 Critical Alert)- Troubleshooting Guide
Purpose This document provides a standardized approach for handling and troubleshooting the Network Down - Boot alert, ensuring quick response to critical incidents and maintaining cluster control and system accessibility. Alert Name Network Down - ...
PSU Error Alert - Troubleshooting Guide
Purpose This document provides a standardized approach for handling and troubleshooting the PSU Error alert, ensuring quick identification of power supply issues and maintaining system power redundancy. Alert Name PSU Error Alert Description This ...