A Linux system administrator notices that despite clearing a substantial amount of data, the 'df' and 'du' commands show significant differences in disk usage reports, and users are unable to create new files. What is the MOST likely cause of this problem?
The file system is corrupted
The file system has reached its maximum number of available inodes
The '/tmp' directory is full
Rogue processes are continuously consuming disk space
The discrepancy between 'df' and 'du' along with the inability to create new files, despite apparent available disk space, points to inode exhaustion. 'df' reports total disk space including used inodes, while 'du' reports actual file data usage. Inode exhaustion occurs when all the available inodes are in use; new files cannot be created even if physical space is available. A corrupted filesystem would also prevent new files from being created, but wouldn't normally cause the discrepancies between 'df' and 'du' focused on inodes. A full '/tmp' directory would cause issues with file creation but is more likely to be related to space, not inodes, and rogue processes consuming disk space would not directly prevent new file creation if inodes were still available.
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 are inodes in a Linux filesystem?
Open an interactive chat with Bash
How can a Linux admin check for inode usage on the system?
Open an interactive chat with Bash
What can cause inode exhaustion and how can it be resolved?