Storage Admin HubConfiguration · Protection · Recovery
All guides/Troubleshooting
Troubleshooting · ONTAP 9

Volume or aggregate full: triage and recovery

Separate logical volume limits from aggregate physical pressure.

Scenario

Example: vol_projects is 96% used while its aggregate is 89% physically used. First identify snapshots, user data, and guarantees before changing either size.

Before you change production

Commands and screens can differ by release and platform. Replace example names and documentation IP addresses. Check prerequisites, impact, current health and rollback with your change owner.

1. Confirm failure domain

  1. Record the EMS message, affected SVM/volume/aggregate, write failures, and client impact. Determine whether the volume is full, the aggregate is physically full, or space guarantees are overallocated.
  2. Compare logical and physical used space and snapshot usage. Do not assume a large client-visible free value means the aggregate has room.
Read-only investigation 
event log show -severity ERROR
storage aggregate show
volume show
volume show-space
volume snapshot show

2. Choose a safe response

  1. If only the volume limit is reached and the aggregate has ample physical headroom, a controlled volume increase may restore writes. Calculate growth and confirm policy first.
  2. If the aggregate is near physical exhaustion, free approved recoverable data, move a volume, or add capacity as supported. Treat metadata and guarantee alerts as urgent.
  3. Review snapshot and SnapMirror dependencies before deleting any recovery point. Never disable snapshots or change retention without the protection owner.
Verify

Writes restored and physical headroom above the agreed operational threshold.

3. Prevent recurrence

  1. Identify the growth source: new files, changed workload, snapshots, clone, or reserved space. Compare actual daily growth to forecast.
  2. Tune alerts, capacity plan, and cleanup ownership. Re-check after one snapshot/replication cycle.
Verify

A measurable capacity trend and next review date are recorded.

If validation fails

  1. If writes fail while the volume reports free space, inspect aggregate physical allocation, guarantees and metadata alerts; client-visible free space is not decisive.
  2. If snapshots dominate used space, determine which copies are retained by policy or replication before removing any approved obsolete copy.
  3. After a capacity action, verify new writes from an affected client and review free space again after the next snapshot or transfer cycle.
Verify

Re-run the original validation and record the observed result, exact error, time, and corrective action.

NetApp references