1
0
mirror of https://github.com/jbranchaud/til synced 2026-01-03 15:18:01 +00:00

Add Running Out Of inode Space as a devops til.

This commit is contained in:
jbranchaud
2015-10-14 08:44:03 -05:00
parent 9bd193b141
commit c76657bb02
2 changed files with 19 additions and 0 deletions

View File

@@ -46,6 +46,7 @@ smart people at [Hashrocket](http://hashrocket.com/).
- [Check The Syntax Of nginx Files](devops/check-the-syntax-of-nginx-files.md)
- [Push Non-master Branch To Heroku](devops/push-non-master-branch-to-heroku.md)
- [Reload The nginx Configuration](devops/reload-the-nginx-configuration.md)
- [Running Out Of inode Space](devops/running-out-of-inode-space.md)
- [Wipe A Heroku Postgres Database](devops/wipe-a-heroku-postgres-database.md)
### git

View File

@@ -0,0 +1,18 @@
# Running Out Of inode Space
Unix systems have two types of storage limitations. The first, and more
common, is a limitation on physical storage used for storing the contents of
files. The second is a limitation on `inode` space which represents file
location and other data.
Though it is uncommon, it is possible to run out of `inode` space before
running out of disk space (run `df` and `df -i` to see the levels of each).
When this happens, the system will complain that there is `No space left on
device`. Both `inode` space and disk space is needed to create a new file.
How can this happen? If lots of directories with lots of empty, small, or
duplicate files are being created, then the `inode` space can be used up
disproportionately to the amount of respective disk space. You'll need to
clean up some of those files before you can continue.
Sources: [this](http://blog.scoutapp.com/articles/2014/10/08/understanding-disk-inodes) and [this](http://www.linux.org/threads/intro-to-inodes.4130/)