home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu!news
- From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
- Newsgroups: comp.os.linux
- Subject: Re: "No free inodes - contact linus" 0.99pl0 kernel
- Date: 23 Dec 1992 14:19:20 -0600
- Organization: Kansas State University
- Lines: 27
- Message-ID: <1hahk8INNjv5@matt.ksu.ksu.edu>
- References: <arumble.725111999@extro.ucc.su.OZ.AU> <1ha97dINNg0b@matt.ksu.ksu.edu> <books.159.0@fsunuc.physics.fsu.edu>
- NNTP-Posting-Host: matt.ksu.ksu.edu
- Keywords: Linux, kernel problem
-
- books@fsunuc.physics.fsu.edu (Roger Books) writes:
-
- >In article <1ha97dINNg0b@matt.ksu.ksu.edu> probreak@matt.ksu.ksu.edu (James Michael Chacon) writes:
- >>In 0.99.1, Linus incorporated the fix for this. There is a constant in
- >>/usr/include/linux/fs.h called NR_INODE which was set to 128 under pl0.
- >>
- >>By changing it to 256, I haven't seen any problems with this happening yet.
- >>
- >>You should be able to get full source, patches against pl0, or a binary image
- >>from either tsx-11.mit.edu or nic.funet.fi.
- >>
- >>James
-
- >Now I am a bit confused. My understanding of a normal unix file system is
- >that the i-nodes are basically used to maintain file location information
- >and that each file, no matter how small, requires an i-node. Obviously
- >this can't be the case here because everyone should easily have more than
- >256 files in the file system. Is the file system here not a ufs file
- >system?
-
- >Roger
- >books@fsunuc.physics.fsu.edu
-
- The inode define just sets how many inodes can be accesswd at once. It was
- never a problem before, so setting it to 255 should be fine for a long while.
-
- James
-