<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Filesystem on LinuxHosted.com</title><link>https://www.linuxhosted.com/tags/filesystem/</link><description>Recent content in Filesystem on LinuxHosted.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>LinuxHosted.com</copyright><lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxhosted.com/tags/filesystem/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux VPS Disk and Inode Cleanup: du, find, lsof</title><link>https://www.linuxhosted.com/post/linux-vps-disk-inode-cleanup/</link><pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.linuxhosted.com/post/linux-vps-disk-inode-cleanup/</guid><description>
&lt;p&gt;&lt;code&gt;No space left on device&lt;/code&gt;. The error stops your application cold, and the first instinct — delete some logs and move on — usually misses what is actually wrong. A full disk on a VPS is rarely one obvious huge file; it is more often a directory you forgot about, a log that a process is still writing to after you &amp;quot;deleted&amp;quot; it, or — the one that fools almost everyone the first time — a disk with plenty of free &lt;em&gt;space&lt;/em&gt; that has run out of &lt;em&gt;inodes&lt;/em&gt;. This guide walks the diagnosis in the order an experienced administrator actually does it, with the three tools that find every case: &lt;code&gt;du&lt;/code&gt;, &lt;code&gt;df&lt;/code&gt;, and &lt;code&gt;lsof&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>