Inode number and disk space

santhoshk · 09-03-2011, 12:57 PM

Hi All,

What is the range of Inode number that can be used by an file system? If the Inode numbers are used on a filesystem would we get "No space Error" ?Please advise.

Thanks

paulsm4 · 09-03-2011, 01:12 PM

An inode number is an integer.

The #/inodes in a filesystem is finite. If you exceed the #/inodes allowed, you cannot create any more files. You must first increase the size of the inode table.

The #/inodes in a filesystem is determined *only* by the capacity of the inode table, *not* by the numeric range of the inode number. Inodes are *not* susceptible to "integer overflow" (like file size could be).

Here's more info:

http://en.wikipedia.org/wiki/Inode

anomie · 09-03-2011, 01:54 PM

And to specifically answer:

Quote:

Originally Posted by santhoshk

What is the range of Inode number that can be used by an file system?

That is determined at filesystem creation time. If not explicitly set, defaults are used. To see the inodes available for an existing filesystem, you can use:

Code:

$ df -i

---

Quote:

Originally Posted by santhoshk

If the Inode numbers are used on a filesystem would we get "No space Error" ?

Yes, that is possible.