Messages in this thread | | | Date | Wed, 15 Jul 1998 11:11:15 +1000 | From | Dancer <> | Subject | Re: Day of panics - 2.0.32 |
| |
Ahhh...It is entirely possible that we blew that limit under load.
Many thanks. (And yes, I assumed the message was fairly outdated)
D
Stephen C. Tweedie wrote: > > Hi, > > On Mon, 13 Jul 1998 20:43:49 +1000, Dancer <dancer@brisnet.org.au> said: > > > Within the next hour, number three and number four go down almost > > simultaneously with: "VFS: No free inodes - contact Linus" > > This is a rather misleading message which we really ought to change! > > That's a configuration issue. The kernel keeps a soft limit on the > number of inodes to guard against denial-of-service problems. The > values can be increased at run-time. You can read the current limits on > file descriptors and inodes by `cat`ing /proc/sys/kernel/file-nr and > .../inode-nr, and you can `echo` new limit values into .../inode-max and > file-max. > > --Stephen
-- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GAT d- s++: a C++++$ UL++++B+++S+++C++H++U++V+++$ P+++$ L+++ E- W+++(--)$ N++ w++$>--- t+ 5++ X+() R+ tv b++++ DI+++ e- h-@ ------END GEEK CODE BLOCK------
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
| |