CI "Disk quota exceeded" (EDQUOT) Writing Files

By Daniel Zoghalchali·Latchkey

A write failed with EDQUOT because a filesystem quota (per-user, per-project, or per-volume) was hit. This can happen even when df shows free bytes, because the limit is a quota, not the disk size.

What this error means

A write fails with Disk quota exceeded while the device still reports free space. Reducing output or running where the quota is higher resolves it with no code change.

tar: bundle.tar: Cannot write: Disk quota exceeded
##[error] Process completed with exit code 2.

Common causes

A per-user or per-project quota is set

Some runner hosts enforce quotas on the home or work volume. Hitting the quota returns EDQUOT regardless of raw free space.

A small overlay or tmpfs volume

Work directories backed by a sized overlay or tmpfs cap usage below the host disk.

How to fix it

Confirm the quota and current usage

Check whether a quota is in force and how much you are using.

quota -s 2>/dev/null || repquota -a 2>/dev/null
df -h .
du -sh ./* 2>/dev/null | sort -rh | head

Write less or use a higher-limit runner

1. Trim large intermediate outputs and clean up between steps.
2. Write big artifacts to a path/volume without a tight quota.
3. Move the job to a runner with more headroom.

How to prevent it

• Know the quota on runner work volumes.
• Avoid writing huge artifacts into quota-limited paths.
• Right-size runners for output-heavy jobs.

Frequently asked questions

Related guides

References

• GitHub Actions documentation