Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
To fix the insufficient inodes issue on a FS shouldn't be involved File System extend or House Keeping of existing File system. Can someone help me to find the actual fix in terms of semaphore tunning stuffs please?
If your filesystem is out of inodes, you didn't create enough when initially formatting. I don't know of a way to add more to an existing system, so I've always had to backup files and reformat to deal with it. The reiserfs filesystem is one that I know allocates inodes dynamically as needed, so it could be used if you have no idea how many you really need. Other filesystems might do that, too.
The best option, if not using JFS or XFS, has been pointed out already, make a backup of your documents and recreate the file system. Since you fail to mention what file system you are using (ext3, ext4, reiser, ...) there's no way anyone can give a more specific answer. The more information you provide, the more adequate an answer will be. You can read some more about inodes here on Wikipedia.
Looking forward to your participation in the forums. Have fun with Linux.
Not that I know of when using ext3. I'm afraid the only way to go is the one pointed out, backing up your data and re-create the file system. The number of inodes can be predefined by setting a different inode size when creating the file system but once it has been created you're 'stuck' with it I'm afraid.
Yes, As i mentioned, there is a way to tune the inode stuffs through semaphore's... I am not sure about that. Anyway thanks for your suggestion
I don't know where you found that statement, but I don't believe it's
correct. One option to deal w/ insufficient inodes (I assume you're
holding vast numbers of little files, I can't think of another way to
run out of inodes) would be to tar files you won't be using frequently,
maybe with a catalog file telling you which tarball has which group
of little files contained. You wouldn't need to compress the tar-ball
as your filesystem size obviously isn't the issue.
I started to doubt myself when OP mentioned semaphores but haven't found anything usefull to up the number of inodes using them. So, misakimurali, would you mind pointing us to where you got that information?