Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have near of 100000 inodes (near of their limit) in my shared hosting (don't ask why), i need every file ! in this way what i can do ? I have too many pictures... (if i store all that's pictures on mysql - one big data file -) can i reduce the inodes count? inodes are associated to internal file info or file content... ?? the ask is: too many small files = too many inodes... one big file = one inode or one big file= too many inodes ??

sorry for my bad english.

share|improve this question

closed as off-topic by EEAA Jul 9 at 1:31

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – EEAA
If this question can be reworded to fit the rules in the help center, please edit the question.

Each single file in a Unix-like OS uses one inode. So as long as it's the inodes count and not disk space that is the limiting factor, if you can work out a scheme where the files are all grouped together into a single large file, that large file will only use a single inode (barring such things as the underlying file system's file size limit and such).

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.