Skip to content

No space left on device – running out of Inodes

One of our development servers went down today. Problems started with deployment script that claimed that claimed “No space left on device”, although partition was not nearly full. If you ever run into such trouble – most likely you have too many small or 0-sized files on your disk, and while you have enough disk space, you have exhausted all available Inodes. Below is the solution for this problem.

1. check available disk space to ensure that you still have some

$ df

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/xvda             33030016  10407780  22622236  32% /
tmpfs                   368748         0    368748   0% /lib/init/rw
varrun                  368748        56    368692   1% /var/run
varlock                 368748         0    368748   0% /var/lock
udev                    368748       108    368640   1% /dev
tmpfs                   368748         0    368748   0% /dev/shm

2. check available Inodes

$ df -i

Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/xvda            2080768 2080768       0  100% /
tmpfs                  92187       3   92184    1% /lib/init/rw
varrun                 92187      38   92149    1% /var/run
varlock                92187       4   92183    1% /var/lock
udev                   92187    4404   87783    5% /dev
tmpfs                  92187       1   92186    1% /dev/shm
If you have IUse% at 100 or near, then huge number of small files is the reason for “No space left on device” errors.

3. find those little bastards

$ for i in /*; do echo $i; find $i |wc -l; done

This command will list directories and number of files in them. Once you see a directory with unusually high number of files (or command just hangs over calculation for a long time), repeat the command for that directory to see where exactly the small files are.

$ for i in /home/*; do echo $i; find $i |wc -l; done

4. once you found the suspect – just delete the files

$ sudo rm -rf /home/bad_user/directory_with_lots_of_empty_files

You’re done. Check the results with df -i command again. You should see something like this:

Filesystem            Inodes   IUsed   IFree IUse% Mounted on

/dev/xvda            2080768  284431 1796337   14% /
tmpfs                  92187       3   92184    1% /lib/init/rw
varrun                 92187      38   92149    1% /var/run
varlock                92187       4   92183    1% /var/lock
udev                   92187    4404   87783    5% /dev
tmpfs                  92187       1   92186    1% /dev/shm
Share

14 Comments

  1. Mads wrote:

    Thanks for sharing, helped me out :)

    Thursday, August 19, 2010 at 22:33 | Permalink
  2. Jack wrote:

    Many thanks for this; ran into the mysterious no space left problem and was baffled, but these instructions worked like a charm.

    Monday, September 27, 2010 at 20:02 | Permalink
  3. philippe wrote:

    Thx :) So helpfull

    Monday, December 13, 2010 at 13:48 | Permalink
  4. chad wrote:

    Great information – This may have resolved several months of scratching our heads trying to figure out why /var showed 52% usage and the disk space was filling up.

    Great info.

    Rgds,

    Chad

    Wednesday, January 5, 2011 at 19:38 | Permalink
  5. Guido wrote:

    Ivan, you’re my hero of the day !

    I thought I have to make a new installation of my Ubuntu-Lucid Server, but you helped my out.
    My Twonky MediaServer Program creates billons of useless files… :-(

    Thx
    Guido

    Wednesday, February 9, 2011 at 21:41 | Permalink
  6. Tikki wrote:

    Very helpful. We were out of imagination to solve a no disk space problem when the disk actually had enough free space :-)

    Thursday, February 17, 2011 at 16:21 | Permalink
  7. Manny wrote:

    Just the cure!

    My /tmp ran of out inodes… mainly in /tmp/orbit-gdm.

    I nuked that folder and went for 100%I to just 1%I usage.

    Thanks!

    Wednesday, March 9, 2011 at 19:11 | Permalink
  8. Chetan wrote:

    You saved lots of time , its happens to my amazon ec2 frequently .

    Saturday, June 11, 2011 at 11:00 | Permalink
  9. Aleksandar wrote:

    Hi, does it cover RH linux as well? I tried this syntax for RH linux bu it doesnt work…

    Wednesday, August 10, 2011 at 9:19 | Permalink
  10. Aleksandar wrote:

    Hi agains ,

    It is working!!
    I’ve just made mistake ..thanks a lot!

    Wednesday, August 10, 2011 at 10:50 | Permalink
  11. Alberto wrote:

    Thanks for the info !
    very useful !

    Greetings

    Monday, October 31, 2011 at 17:21 | Permalink
  12. Thanks man…… Thank u very much…..

    Sunday, November 20, 2011 at 20:58 | Permalink
  13. Some times is difficult to erase the files with the command rm -f -r /tmp/*

    In such situation you could you use the next command:

    sudo find / -type f -print | xargs — sudo rm -f –

    This tip is for all the people that stay in the fire line jaja lol ; )

    Thursday, December 22, 2011 at 22:17 | Permalink
  14. Abser wrote:

    Just Rocking ! Gr8.

    Monday, January 16, 2012 at 11:17 | Permalink

One Trackback/Pingback

  1. problem mit vserver nichts geht mehr on Sunday, October 23, 2011 at 18:42

    [...] [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *
*
*