{"id":9138,"date":"2026-06-09T12:36:00","date_gmt":"2026-06-09T07:06:00","guid":{"rendered":"https:\/\/www.veeble.com\/kb\/?p=9138"},"modified":"2026-06-09T12:36:00","modified_gmt":"2026-06-09T07:06:00","slug":"fix-no-space-left-on-device-linux","status":"publish","type":"post","link":"https:\/\/www.veeble.com\/kb\/fix-no-space-left-on-device-linux\/","title":{"rendered":"How to Fix &#8220;No Space Left on Device&#8221; Error on Linux (2026)"},"content":{"rendered":"\n<p>The <strong>&#8220;No space left on device&#8221;<\/strong> error usually happens for one of two reasons: either the disk is full, or the filesystem has run out of inodes. While both cause the same error, the way you diagnose and fix them is different.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#what-causes-this-error\">What Causes This Error?<\/a><ul><li><a href=\"#disk-full\">Disk Full<\/a><\/li><li><a href=\"#inode-exhaustion\">Inode Exhaustion<\/a><\/li><\/ul><\/li><li><a href=\"#step-1-check-if-the-disk-is-actually-full\">Step 1: Check If the Disk Is Actually Full<\/a><\/li><li><a href=\"#step-2-check-inode-usage\">Step 2: Check Inode Usage<\/a><\/li><li><a href=\"#step-3-find-what-is-consuming-disk-space\">Step 3: Find What Is Consuming Disk Space<\/a><ul><li><a href=\"#identify-large-directories\">Identify large directories<\/a><\/li><li><a href=\"#use-ncdu-for-interactive-exploration\">Use ncdu for interactive exploration<\/a><\/li><li><a href=\"#find-the-largest-individual-files\">Find the largest individual files<\/a><\/li><\/ul><\/li><li><a href=\"#step-4-free-up-disk-space\">Step 4: Free Up Disk Space<\/a><ul><li><a href=\"#clean-the-package-cache\">Clean the package cache<\/a><\/li><li><a href=\"#remove-old-kernels\">Remove old kernels<\/a><\/li><li><a href=\"#truncate-bloated-log-files\">Truncate bloated log files<\/a><\/li><li><a href=\"#remove-large-files-that-are-no-longer-needed\">Remove large files that are no longer needed<\/a><\/li><li><a href=\"#clear-docker-resources-if-applicable\">Clear Docker resources (if applicable)<\/a><\/li><\/ul><\/li><li><a href=\"#step-5-fix-inode-exhaustion\">Step 5: Fix Inode Exhaustion<\/a><ul><li><a href=\"#find-which-directory-has-the-most-files\">Find which directory has the most files<\/a><\/li><li><a href=\"#clean-postfix-mail-queue\">Clean Postfix mail queue<\/a><\/li><li><a href=\"#clean-exim-mail-queue\">Clean Exim mail queue<\/a><\/li><li><a href=\"#remove-php-session-files\">Remove PHP session files<\/a><\/li><li><a href=\"#clear-temporary-directories\">Clear temporary directories<\/a><\/li><li><a href=\"#a-note-on-inode-limits\">A note on inode limits<\/a><\/li><\/ul><\/li><li><a href=\"#step-6-verify-the-fix\">Step 6: Verify the Fix<\/a><\/li><li><a href=\"#prevention\">Prevention<\/a><\/li><li><a href=\"#conclusion\">Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n\n\n<h2 class=\"wp-block-heading has-ast-global-color-0-color has-text-color has-link-color wp-elements-32ac2c867df2f394553876b721902cb6\" id=\"what-causes-this-error\">What Causes This Error?<\/h2>\n\n<h4 class=\"wp-block-heading has-ast-global-color-0-color has-text-color has-link-color wp-elements-8fb6ecb558bb87197005d408c3b4a6fd\" id=\"disk-full\">Disk Full<\/h4>\n\n\n<p class=\"has-white-color has-text-color has-background has-link-color wp-elements-24911546194b30949fc2535cfcf3a4d6\" style=\"background-color:#6d5cd0\">This is the most common cause. A partition has reached its storage limit, so Linux can no longer create or modify files. Large log files, database backups, uploaded content, Docker volumes, and application caches are often responsible. Once the partition reaches 100% usage, write operations start failing immediately.<\/p>\n\n\n<h4 class=\"wp-block-heading has-ast-global-color-0-color has-text-color has-link-color wp-elements-4f49bb248fc6d2619abf59dcbad339f1\" id=\"inode-exhaustion\">Inode Exhaustion<\/h4>\n\n\n<p class=\"has-white-color has-text-color has-background has-link-color wp-elements-78c1ba54f555f5882fb86e9b2cdf97d8\" style=\"background-color:#6d5cd0\">Sometimes the disk still has free space available, but Linux is unable to create new files. This happens when the filesystem runs out of inodes, which are used to keep track of files and directories. In this situation, <code>df -h<\/code> may show available space even though file creation and write operations continue to fail.<br><br>This issue is commonly caused by large mail queues, PHP session files that accumulate over time, application caches containing huge numbers of small files, or temporary files that are never cleaned up. Because the symptoms look almost identical to a full disk, many administrators overlook inode usage during troubleshooting.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"step-1-check-if-the-disk-is-actually-full\">Step 1: Check If the Disk Is Actually Full<\/h2>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-6248eeb6b4d1a9bbc4daa6e7488dd552\"><code>df -h<\/code><\/pre>\n\n\n\n<p>Sample output:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot1-4.jpg\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"286\" src=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot1-4-1024x286.jpg\" alt=\"\" class=\"wp-image-9144\" srcset=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot1-4-1024x286.jpg 1024w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot1-4-300x84.jpg 300w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot1-4-768x214.jpg 768w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot1-4.jpg 1289w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>Check the <strong>Use%<\/strong> column first. If any partition shows <strong>100% usage<\/strong>, you&#8217;ve likely found the source of the problem. Pay attention to the <strong>Mounted on<\/strong> column as well, since it tells you where to focus your cleanup efforts. If nothing is at 100% but you&#8217;re still seeing write errors, move on to the next step and check inode usage.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"step-2-check-inode-usage\">Step 2: Check Inode Usage<\/h2>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-6c8683f5991597e1301631617ad10b63\"><code>df -i<\/code><\/pre>\n\n\n\n<p>Sample output:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot2.jpg\"><img decoding=\"async\" width=\"1024\" height=\"261\" src=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot2-1024x261.jpg\" alt=\"\" class=\"wp-image-9145\" srcset=\"https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot2-1024x261.jpg 1024w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot2-300x76.jpg 300w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot2-768x196.jpg 768w, https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/screenshot2.jpg 1414w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p>Check the <strong>IUse%<\/strong> column. If a partition shows <strong>100% inode usage<\/strong>, Linux won&#8217;t be able to create new files even if there is still free disk space available. This is known as <strong>inode exhaustion<\/strong>. If you find a partition at 100%, skip ahead to <strong>Step 5<\/strong> to identify what is consuming the inodes.<\/p>\n\n\n\n<p>If both <code>df -h<\/code> and <code>df -i<\/code> look normal, the issue may be related to something less common, such as a bind mount problem or an NFS-related issue.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"step-3-find-what-is-consuming-disk-space\">Step 3: Find What Is Consuming Disk Space<\/h2>\n\n<h3 class=\"wp-block-heading\" id=\"identify-large-directories\">Identify large directories<\/h3>\n\n\n<p>Start from the filesystem root and work down:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-6fa8b9b2189f709bf34ffbd4831e165c\"><code>du -sh \/* 2&gt;\/dev\/null | sort -rh | head -20<\/code><\/pre>\n\n\n\n<p>Then drill into the largest directory:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-7fe09fc6b0aafd65902574c9242924b3\"><code>du -sh \/var\/* 2&gt;\/dev\/null | sort -rh | head -20<\/code><\/pre>\n\n\n\n<p>Keep narrowing until you reach the specific directory or file responsible.<\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"use-ncdu-for-interactive-exploration\">Use ncdu for interactive exploration<\/h3>\n\n\n<p><code>ncdu<\/code> provides an interactive tree view and is faster to navigate on large filesystems:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-e549cc51085ae13a4805e71816cfaf2f\"><code># Debian\/Ubuntu\napt install ncdu\n\n# CentOS\/RHEL\nyum install ncdu\n\nncdu \/<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"find-the-largest-individual-files\">Find the largest individual files<\/h3>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-27f52aafe5623966fdd635dc71c521ae\"><code>find \/ -xdev -type f -printf '%s %p\\n' 2&gt;\/dev\/null | sort -rn | head -20<\/code><\/pre>\n\n\n\n<p>The <code>-xdev<\/code> flag limits the search to the current filesystem, so mounted filesystems are skipped. This makes it easier to identify what&#8217;s using space on the affected partition.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"step-4-free-up-disk-space\">Step 4: Free Up Disk Space<\/h2>\n\n<h3 class=\"wp-block-heading\" id=\"clean-the-package-cache\">Clean the package cache<\/h3>\n\n\n<p><strong>Debian\/Ubuntu:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-21600dc87428a0b850606f62c1a7891d\"><code>apt clean\napt autoremove --purge<\/code><\/pre>\n\n\n\n<p><strong>CentOS\/RHEL:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-10a523a16d24b57f28c5a1f180cf8725\"><code>yum clean all\ndnf clean all<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"remove-old-kernels\">Remove old kernels<\/h3>\n\n\n<p><strong>Debian\/Ubuntu:<\/strong><\/p>\n\n\n\n<p>Old kernels are removed automatically by <code>apt autoremove<\/code> in most cases. Verify with:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-2d370c4d507d18ed6d678efb13fb457f\"><code>dpkg --list | grep linux-image<\/code><\/pre>\n\n\n\n<p>Then remove a specific old kernel:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-9976c3217367df231ad7c0cd8b60134d\"><code>apt remove --purge linux-image-&lt;version&gt;<\/code><\/pre>\n\n\n\n<p><strong>CentOS\/RHEL:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-c5330a34d9da1e0563c35cd914f20b32\"><code>rpm -q kernel\npackage-cleanup --oldkernels --count=1<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"truncate-bloated-log-files\">Truncate bloated log files<\/h3>\n\n\n<p>Do not delete active log files. Truncate them instead to avoid breaking file handles held by running services:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-71439c37d2054e3a1e371d6d1a8cb218\"><code>truncate -s 0 \/var\/log\/syslog\ntruncate -s 0 \/var\/log\/auth.log<\/code><\/pre>\n\n\n\n<p>Find all large log files in one pass:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-bc1bcb5e6d37cba535f7fd6b6b6fbc97\"><code>find \/var\/log -type f -size +100M -ls<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"remove-large-files-that-are-no-longer-needed\">Remove large files that are no longer needed<\/h3>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-4f956a44b67df7a75325c60bdc4ca301\"><code>find \/ -xdev -type f -size +500M 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p>Review the output before deleting anything.<\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"clear-docker-resources-if-applicable\">Clear Docker resources (if applicable)<\/h3>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-530e6e95be1518e764d455fea73d6f34\"><code>docker system prune -a<\/code><\/pre>\n\n\n\n<p>This removes stopped containers, unused images, unused networks, and build cache. Add <code>-f<\/code> to skip the confirmation prompt.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"step-5-fix-inode-exhaustion\">Step 5: Fix Inode Exhaustion<\/h2>\n\n\n<p>The goal is to identify the directory holding the large number of small files and remove them.<\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"find-which-directory-has-the-most-files\">Find which directory has the most files<\/h3>\n\n\n<p>This loop counts files per top-level directory:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-960e7a6168ec99b9865cc9cde11918a6\"><code>for i in \/*; do echo $(find \"$i\" -xdev | wc -l) \"$i\"; done 2&gt;\/dev\/null | sort -rn | head -10<\/code><\/pre>\n\n\n\n<p>Then drill into the top result:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-454fd549d3055934ddc845dfdfb02793\"><code>for i in \/var\/*; do echo $(find \"$i\" -xdev | wc -l) \"$i\"; done 2&gt;\/dev\/null | sort -rn | head -10<\/code><\/pre>\n\n\n\n<p>Continue until you reach the specific subdirectory with the excessive file count.<\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"clean-postfix-mail-queue\">Clean Postfix mail queue<\/h3>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-0676eabd89efb673de0c172a7844ab31\"><code>postsuper -d ALL<\/code><\/pre>\n\n\n\n<p>To delete only deferred messages:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-efc8bfddd15c3f6c4cf77bfa8b66bc07\"><code>postsuper -d ALL deferred<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"clean-exim-mail-queue\">Clean Exim mail queue<\/h3>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-ebd860b3d8096dd5072bf78561f60938\"><code>exim -bp | exiqgrep -i | xargs exim -Mrm<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"remove-php-session-files\">Remove PHP session files<\/h3>\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-303aa93daa258bff5bcdbd00d32fd2b7\"><code>find \/var\/lib\/php\/sessions -type f -delete<\/code><\/pre>\n\n\n\n<p>On older setups where sessions land in <code>\/tmp<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-a7715dfd1aeb19a327836e941151933f\"><code>find \/tmp -name 'sess_*' -type f -delete<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"clear-temporary-directories\">Clear temporary directories<\/h3>\n\n\n<p>Remove files older than 7 days to avoid deleting anything actively in use:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-4448baae044e628d341f4b42239371ad\"><code>find \/tmp -type f -atime +7 -delete\nfind \/var\/tmp -type f -atime +7 -delete<\/code><\/pre>\n\n\n<h3 class=\"wp-block-heading\" id=\"a-note-on-inode-limits\">A note on inode limits<\/h3>\n\n\n<p>Inodes cannot be added to an existing ext4 filesystem. If you keep running into inode exhaustion, it may be worth moving to a larger filesystem or switching to XFS, which handles inode allocation differently and is generally less prone to this issue. Since this requires reformatting, make sure you have a full backup before making any changes.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"step-6-verify-the-fix\">Step 6: Verify the Fix<\/h2>\n\n\n<p>Recheck both disk space and inode usage:<\/p>\n\n\n\n<pre class=\"wp-block-code has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-9c35b2281f9c52ebedb08d73bc57f970\"><code>df -h\ndf -i<\/code><\/pre>\n\n\n\n<p>The previously full partition should now show available space or available inodes. Confirm by attempting the write operation that was failing, or restart the service that was generating the error. For web servers and databases, a restart after resolving disk issues is good practice regardless, as some services cache the error state internally.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"prevention\">Prevention<\/h2>\n\n\n<p><strong>Configure logrotate for all application log files.<\/strong> System logs under <code>\/var\/log<\/code> are handled by default logrotate rules, but application-specific logs are frequently not. Add configurations to <code>\/etc\/logrotate.d\/<\/code> for any application writing its own log files, and use the <code>compress<\/code> and <code>maxsize<\/code> directives to cap file sizes.<\/p>\n\n\n\n<p><strong>Set up disk and inode monitoring.<\/strong> Alert at 80% usage for both disk blocks and inodes. A Zabbix or Nagios check handles this natively, and a simple cron script using <code>df<\/code> works for minimal setups. Catching the problem before 100% avoids a service outage.<\/p>\n\n\n\n<p><strong>Automate PHP session cleanup.<\/strong> PHP&#8217;s built-in session garbage collection is not always reliable under high traffic. A daily cron job handles it more predictably:<\/p>\n\n\n\n<pre class=\"wp-block-code has-vivid-green-cyan-color has-black-background-color has-text-color has-background has-link-color wp-elements-df04c8329b466df6fb4bd3442d56bcd8\"><code>0 3 * * * find \/var\/lib\/php\/sessions -type f -mtime +1 -delete<\/code><\/pre>\n\n\n\n<p><strong>Configure mail server queue limits.<\/strong> Postfix and Exim support queue size limits and bounce handling policies that prevent runaway growth. Review <code>maximal_queue_lifetime<\/code> and <code>bounce_queue_lifetime<\/code> in Postfix, or <code>queue_run_max_msgs<\/code> in Exim.<\/p>\n\n\n\n<p><strong>Use <code>tmpwatch<\/code> or <code>systemd-tmpfiles<\/code> to manage <code>\/tmp<\/code> automatically.<\/strong> On systems using systemd, <code>\/etc\/tmpfiles.d\/<\/code> rules can enforce automatic cleanup of stale temporary files.<\/p>\n\n\n<h2 class=\"wp-block-heading\" id=\"conclusion\">Conclusion<\/h2>\n\n\n<p>Resolving the immediate error is straightforward once you identify whether it is a disk space problem or an inode exhaustion problem. If your VPS is hitting these limits repeatedly despite regular cleanup, the storage allocation may simply be too small for the current workload. Veeble&#8217;s <a href=\"https:\/\/veeble.com\/vps-hosting\/\" target=\"_blank\" rel=\"noopener\">VPS hosting plans<\/a> offer scalable storage, so you can increase disk capacity without reformatting or migrating. Upgrade before the next outage rather than after it.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The &#8220;No space left on device&#8221; error usually happens for one of two reasons: either the disk is full, or the filesystem has run [&hellip;]<\/p>\n","protected":false},"author":15,"featured_media":9150,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[5],"tags":[92,90,91,67,89,86,68],"class_list":["post-9138","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","tag-command-line","tag-disk-management","tag-kvm-vps","tag-linux","tag-server-management","tag-troubleshooting","tag-vps"],"uagb_featured_image_src":{"full":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/articleimage.jpg",1536,1024,false],"thumbnail":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/articleimage-150x150.jpg",150,150,true],"medium":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/articleimage-300x200.jpg",300,200,true],"medium_large":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/articleimage-768x512.jpg",768,512,true],"large":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/articleimage-1024x683.jpg",1024,683,true],"1536x1536":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/articleimage.jpg",1536,1024,false],"2048x2048":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/06\/articleimage.jpg",1536,1024,false]},"uagb_author_info":{"display_name":"Nasarul Naseer","author_link":"https:\/\/www.veeble.com\/kb\/author\/nasarulnaseer\/"},"uagb_comment_info":0,"uagb_excerpt":"The &#8220;No space left on device&#8221; error usually happens for one of two reasons: either the disk is full, or the filesystem has run [&hellip;]","_links":{"self":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9138","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/comments?post=9138"}],"version-history":[{"count":4,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9138\/revisions"}],"predecessor-version":[{"id":9149,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9138\/revisions\/9149"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/media\/9150"}],"wp:attachment":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/media?parent=9138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/categories?post=9138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/tags?post=9138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}