HTTP 507 Insufficient Storage — Server Disk Space Exhausted

Overview

HTTP 507 Insufficient Storage means the server cannot store the representation needed to complete the request, typically due to exhausted disk space.

Key Details

• Originally from WebDAV (RFC 4918) but applicable to any storage scenario
• Server ran out of disk space, quota, or storage allocation
• Can affect file uploads, database writes, log files, and temporary files
• Different from 413 Payload Too Large — 507 is server storage, 413 is request size
• May also indicate database storage quota exceeded

Common Causes

• Server disk space full from logs, temp files, or uploads
• Database storage quota exceeded
• Cloud storage bucket hitting its quota limit
• Temporary files not being cleaned up properly
• Large log files consuming all available disk space

Steps

1. 1Check server disk space: df -h on Linux/Mac
2. 2Find large files: du -sh /* | sort -rh | head -20
3. 3Clean up old logs: find /var/log -name '*.gz' -mtime +30 -delete
4. 4Set up log rotation with logrotate to prevent future disk exhaustion
5. 5Increase disk allocation or add additional storage if consistently running low

Tags

More in 5xx Server Error

Frequently Asked Questions