A Linux-based web application server suddenly stops writing to its access logs, and some POST requests return HTTP 500 errors. The administrator checks disk usage and sees the following:
The df output shows the root (/) filesystem at 100 percent utilization with 0 GB available. When a filesystem is completely full the OS can no longer create or extend files-including log files and temporary data needed by web applications-so writes fail and services begin returning errors. Clearing or expanding the partition restores normal operation. The other choices do not match the evidence provided: swap exhaustion would appear in memory, not disk, a RAID controller battery issue would not produce a 100 percent full filesystem, and limited free space on /boot affects only kernel updates or boot-time operations, not live web transactions.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What does 'HTTP 500 error' mean?
Open an interactive chat with Bash
Why does a full root filesystem affect server operations?
Open an interactive chat with Bash
How can the administrator resolve a full filesystem issue?