Back to All Scenarios
PASSEDcache / disk_full
Redis 7.2 Data Directory Full — Writes Failing on Amazon Linux 2023
The partition containing Redis 7.2 data has reached capacity. All write operations are failing. Read-only mode may be engaged.
Pattern
DISK_FULL
Severity
CRITICAL
Confidence
72%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | DISK_FULL | DISK_FULL | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Amazon Linux 2023. Redis 7.2 data directory on 401GB partition at 100%. Data growth rate: 8GB/day. No disk space alerting configured.
Injected Error Messages (1)
Redis 7.2 disk full on Amazon Linux 2023 — no space left on device, data directory partition 100% full (401GB), redis-server ENOSPC, all write operations failing
Neural Engine Root Cause Analysis
Disk space exhaustion detected — the filesystem has reached capacity, preventing applications from writing data, logs, or temporary files. This can cause databases to crash, services to fail, and logging to stop (masking further issues). Inode exhaustion can also present as 'no space left' even when disk space appears available.
Remediation Plan
1. Identify the fullest filesystems with 'df -h' and check inode usage with 'df -i'.
2. Find and remove large unnecessary files: 'find / -type f -size +100M -exec ls -lh {} \;'.
3. Clear old log files, compress rotated logs, and verify logrotate is configured correctly.
4. Check for runaway log growth from verbose application logging.
5. Expand the volume or add additional storage if the data growth is legitimate.
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnpd9h02d8lig7qlcjm48j