When a Linux server reports a full disk, this guide walks you through eight essential commands to diagnose whether the issue is actual space exhaustion, inode depletion, lingering deleted files, or I/O bottlenecks, and provides a systematic cleanup workflow for production environments.
A senior cloud operations engineer receives a P1 alert for a web‑gateway server nearing 100% /var disk usage, then systematically logs in, diagnoses the log‑file bloat with df, du, and tail, truncates the offending debug log, and implements post‑mortem fixes to prevent recurrence.
This article introduces five essential Linux performance monitoring commands—vmstat, iostat, free, df, and sar—detailing their purpose, key options, example usages, and the meaning of each output column to help you effectively track system resources.
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 introduces five Linux commands—vmstat, iostat, free, df, and sar—explaining their purpose, common options, example usages, and the meaning of each column in their output to help you monitor memory, CPU, I/O, and filesystem performance in real time.
When a Linux server triggers a disk‑space alert, you can pinpoint the offending directories or files by using df to view overall usage, du (with depth or max‑depth) or find to list large items, and lsof +L1 to detect deleted files still holding space, then optionally adjust reserved space with tune2fs.
This guide walks through a real‑world deployment issue where one node failed to start due to a full disk, showing how to verify overall and per‑directory disk usage with df and du commands, interpret their output, and locate large files or directories.
This guide explains how to use the Linux df and du commands to check overall disk space, view partition types, inspect inode information, and determine the size of specific files or directories, with examples and options for human‑readable output.
This guide walks you through key Linux commands such as top, free, iostat, netstat, df, and du, explaining each output field, how to interpret system load, memory usage, CPU statistics, network connections, and disk space to quickly diagnose production issues.
This guide explains how to use the Linux df command with various options to display filesystem disk space, inode usage, and filesystem types in human‑readable, kilobyte, megabyte, or gigabyte formats, and shows how to filter or exclude specific filesystem types.
This guide explains how to diagnose unexpected disk usage on Linux servers by using df to view overall usage, du and find to pinpoint large directories or files, and lsof to uncover deleted files that still hold space, plus how to adjust reserved space with tune2fs.
This guide explains how to use the Linux df command with real‑world examples, covering human‑readable output, inode statistics, total usage, filesystem types, inclusion/exclusion filters, specific mount points, and virtual filesystems to help you monitor disk space effectively.
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 the Linux commands du and df often return mismatched root partition sizes, detailing five underlying reasons such as deleted open files, reserved space, hidden files, mounted directories, and the fundamental differences between how du and df calculate disk usage.
Learn step-by-step Linux techniques—including df, du, find, and lsof commands—to pinpoint large directories or files, filter results, handle hidden space consumption, and adjust reserved filesystem space, ensuring you can efficiently resolve unexpected disk usage issues on your servers.
Learn how to quickly check available disk space on Linux servers using five built‑in commands—df, du, ls, stat, and fdisk—plus handy GUI tools, with practical options and examples to help you clean up storage efficiently.
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.
This article analyzes why the Linux commands du and df often report inconsistent disk usage, detailing the underlying file system structures, inode and block allocation, how each tool gathers statistics, and the impact of mounted partitions and deleted-but‑still‑referenced files.
The article explains why Linux’s du and df commands often report inconsistent disk usage, detailing the underlying file‑system structures such as inodes, block maps, and superblocks, the processes of file creation and deletion, and how mounted partitions, open file handles, and stat calls affect each tool’s calculations.
This guide walks through essential Linux command‑line utilities—df, pydf, fdisk and sfdisk—showing how to display disk usage, list partitions, and query specific devices, with installation tips, example outputs, and practical options for clear monitoring.
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.
This guide explains why removing a file with rm doesn't always release space, demonstrates creating a large test file, shows how open file handles keep space occupied, and provides commands to identify and release such hidden usage.
This guide introduces key Linux commands such as ls, stat, df, du, and fdisk, explains their most useful options, shows how to interpret their output, and provides practical tips for analyzing disk usage and safely reclaiming space on servers.
This guide introduces key Linux commands—such as uptime, who, uname, du, df, free, pmap, vmstat, ifconfig, ip, netstat, top, and pstree—to help you quickly assess system status, resource usage, and process relationships, enabling effective troubleshooting and maintenance.
This guide explains essential Linux storage commands—including fdisk, df, du, mount, umount—covers automatic mounting via /etc/fstab, details disk partitioning with fdisk, and demonstrates how to format partitions using mkfs, providing practical examples for each operation.
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.
This article explains why the Linux commands df and du often report different disk usage figures, detailing three main causes—reserved space, phantom (deleted) files, and data present before mounting—and provides concrete commands and steps to identify and resolve each discrepancy.
This guide explains three practical methods—using df, mount -l, and reading /etc/mtab—to list Linux mount points together with their associated disks or logical volumes, highlighting each command's output format and limitations.
When managing Linux servers, the du and df commands often show mismatched disk usage figures, and this article explains the three main reasons—reserved space, phantom files, and uncounted data during mount operations—and how to diagnose and resolve each discrepancy.
When managing Linux servers, the df and du commands often show mismatched disk usage figures, and this article explains the three main causes—reserved space, phantom files, and uncounted data—along with how to identify and resolve each discrepancy.
