ZFS Pool Capacity Warning Alert - Troubleshooting Guide

KB 715314 - 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

Alert Description

This alert is triggered when ZFS pool utilization exceeds 85%, indicating that the storage pool is nearing capacity limits.
High utilization can lead to:
  1. Performance degradation
  2. Increased latency
  3. Risk of pool exhaustion
If not addressed, it may eventually result in:
  1. Write failures
  2. Application impact
  3. Potential service disruption

Severity

P3 – Medium Impact

Possible Causes

  1. High data ingestion or workload growth
  2. Lack of storage cleanup or retention policies
  3. Snapshot accumulation
  4. Inefficient storage utilization
  5. Unexpected data spikes

L1 Engineer Actions

Step 1 – Log the Alert

  1. Log in to the monitoring system
  2. Review alert summary and affected pool 

Step 2 – Create Ticket

  1. Inform L2 team
  2. Create an internal ticket including:
    1. Alert name
    2. Hostname
    3. Pool name
    4. Current utilization (%)
    5. Timestamp

Step 3 – Escalation (If required)

  1. Share alert details with L2 team for further analysis

Step 4 – Documentation

  1. After confirmation with L2:
    1. Update Issue Master Sheet
    2. Ensure proper tracking of the issue

L2 Engineer Actions

Step 1 – Log Pool Usage

  1. Record current pool utilization
  2. Identify growth trend if historical data is available

Step 2 – Check ZFS Pool Status

zpool status
zfs list
  1. Verify pool health
  2. Check space usage across datasets

Step 3 – Analyze Storage Consumption

  1. Identify:
    1. Large datasets
    2. Snapshot usage
    3. Unused or stale data

Step 4 – Take Preventive Actions

  1. Clean up unnecessary data (if applicable)
  2. Remove unused snapshots
  3. Plan for storage expansion if required

Step 5 – OEM Escalation (If required)

  1. If capacity issue is related to:
    1. Hardware limitation
    2. Expansion requirement
  2. Raise a request with OEM/vendor

Resolution

The issue is considered resolved when:
  1. ZFS pool utilization is reduced below threshold
  2. Adequate free space is available
  3. No risk of immediate capacity exhaustion
  4. Alert is cleared

Escalation

  1. L1 → L2: For analysis and validation
  2. L2 → OEM/Vendor: If storage expansion or hardware support is required