Diagnosing Deployment Failures: Using Linux Disk Commands to Find Full Partitions
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.
During a test deployment using a web publishing platform, one of two nodes failed to start, causing the TPS to remain low. The deployment record showed SUCCESS, but the log revealed that the failed node could not run because the disk was full.
Error log:
Command to view overall disk space:
df -hIf you only need the usage of the current directory, use:
du --max-depth=1 -hThe -h flag makes the sizes human‑readable (adds K, M, G units). The output lists the size of each subdirectory on the first n‑1 lines, with the total size on the last line.
To get the size of a single file or directory, run:
du -shAnother equivalent command is:
du --max-depth=0 -hIn the manual, --max-depth=0 is described as having the same effect as the -s option.
You can also specify a path to check a particular location, for example:
du -sh /root/swSigned-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
