1 views collected around this technical thread.
This article walks through troubleshooting a failed deployment caused by a full disk, showing how to use df -h to check overall disk usage and various du options (including --max-depth and -sh) to pinpoint large directories and resolve the issue.
This guide explains how to use the Linux df and du commands to inspect disk space, interpret their options such as -h, -k, -i, and -T, view partition usage, directory-specific usage, inode information, and avoid common pitfalls when measuring file sizes.
This article explains three common Linux commands—ls, du, and stat—for checking file sizes, showing the exact syntax, example usage with a sample file, and how each command displays size information, including human‑readable formats.
This guide shows step‑by‑step Linux commands—df, du, find, lsof, and tune2fs—to pinpoint large directories, uncover hidden space used by deleted files, and adjust reserved root space, helping you resolve mysterious disk‑space alerts efficiently.
This article explains why Linux utilities like du and ls can report dramatically different file sizes, introduces the concept of sparse files, and shows practical commands to identify and correctly handle them on Unix-like systems.
This guide explains how to use Linux commands such as df, du, find, and lsof to quickly locate directories, files, or deleted resources that are consuming disk space, and shows how to adjust reserved space with tune2fs to recover seemingly missing storage.
The article explains why a Linux system may report a full disk even after deleting files, detailing how open file handles keep space occupied, and walks through the virtual file system architecture—including superblocks, inodes, file and dentry objects—while demonstrating diagnostic commands like df, du, lsof, and illustrating link types and file‑process interactions.
A CentOS web server reports 100% disk usage despite du -sh /* showing far less space used, which is caused by Apache/Tomcat logs being cleared while the services are running, and the issue is resolved by restarting the services and properly cleaning old log files.