UFS , SVR4, and inodes limits

UFS , SVR4, and inodes limits

Post by Hoyt A. Stearns j » Fri, 07 Aug 1992 10:45:26

In UHC SVR4,  an artificial limit of 64000 inodes is placed on UFS file
systems (mkfs -C).  I re-created the filesystem without the "-C",
but the df command reports (accurately) the limit is still there.
the mtune file shows an upper limit of 1300 inode blocks, which I set.

With the rebuilt file system, can I change mtune to have an upper limit of
0x7fffffff (unlimited)?  What else need I do?

Thanks in advance for any help.


4131 E. Cannon Dr. |isus.tnet.com  | Advancing Dewey B. Larson's Reciprocal  |
Phoenix, AZ. 85028 |ncar!enuucp!   | System- a unified physical theory.      |
voice_602_996_1717 telesys!isus!hoyt The Universe in two postulates!_________|


1. grow inodes: inode-max limit reached error.

I run a small shell service and now after about a week and always after cron
jobs by my users, I'm getting this error (which pretty much makes the
machine not usable): "grow inodes: inode-max limit reached". It looks like a
person's crontab job is opening up WAY too many files or soemthing over the
course of time. How do I prevent this from happening?

Debian 2.2 unstable - 2.2.14+lids+ow2



2. help with security

3. grow-inodes: inode-max limit reached

4. Help with error messages...

5. UFS filesystem as root on UHC SVR4

6. Solaris8 and DNS

7. SVR4 filesystem? s5 ufs

8. Daily and Insecurity output

9. Maximum inode number per UFS file system

10. Lots of inodes on a big disk on SVR4

11. Access Control Lists and UFS inodes

12. How to tell which process(es) have a given file/inode open under SVr4?

13. inodes in ufs file system