Commit a75c6589 authored by Stephen Kitt's avatar Stephen Kitt Committed by Jonathan Corbet

docs: sysctl/fs: remove references to inode-max

inode-max was removed in 2.3.20pre1, remove references to it in the
sysctl documentation.
Signed-off-by: default avatarStephen Kitt <steve@sk2.org>
Link: https://lore.kernel.org/r/20220930102937.135841-2-steve@sk2.orgSigned-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 554d4389
......@@ -33,7 +33,6 @@ Currently, these files are in /proc/sys/fs:
- dquot-nr
- file-max
- file-nr
- inode-max
- inode-nr
- inode-state
- nr_open
......@@ -136,18 +135,12 @@ enough for most machines. Actual limit depends on RLIMIT_NOFILE
resource limit.
inode-max, inode-nr & inode-state
---------------------------------
inode-nr & inode-state
----------------------
As with file handles, the kernel allocates the inode structures
dynamically, but can't free them yet.
The value in inode-max denotes the maximum number of inode
handlers. This value should be 3-4 times larger than the value
in file-max, since stdin, stdout and network sockets also
need an inode struct to handle them. When you regularly run
out of inodes, you need to increase this value.
The file inode-nr contains the first two items from
inode-state, so we'll skip to that file...
......@@ -156,11 +149,10 @@ The actual numbers are, in order of appearance, nr_inodes,
nr_free_inodes and preshrink.
Nr_inodes stands for the number of inodes the system has
allocated, this can be slightly more than inode-max because
Linux allocates them one pageful at a time.
allocated.
Nr_free_inodes represents the number of free inodes (?) and
preshrink is nonzero when the nr_inodes > inode-max and the
preshrink is nonzero when the
system needs to prune the inode list instead of allocating
more.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment