Commit 033bfb1a authored by David Chinner's avatar David Chinner Committed by Lachlan McIlroy

[XFS] Update XFS Documentation for ikeep and ihashsize

Update xfs docs for:
* In memory inode hashes has been removed.
* noikeep is now the default.

SGI-PV: 969561
SGI-Modid: 2.6.x-xfs-melb:linux:29481b
Signed-off-by: default avatarDavid Chinner <dgc@sgi.com>
Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
Signed-off-by: default avatarTim Shimmin <tes@sgi.com>
parent e687330b
...@@ -52,16 +52,14 @@ When mounting an XFS filesystem, the following options are accepted. ...@@ -52,16 +52,14 @@ When mounting an XFS filesystem, the following options are accepted.
and also gets the setgid bit set if it is a directory itself. and also gets the setgid bit set if it is a directory itself.
ihashsize=value ihashsize=value
Sets the number of hash buckets available for hashing the In memory inode hashes have been removed, so this option has
in-memory inodes of the specified mount point. If a value no function as of August 2007. Option is deprecated.
of zero is used, the value selected by the default algorithm
will be displayed in /proc/mounts.
ikeep/noikeep ikeep/noikeep
When inode clusters are emptied of inodes, keep them around When ikeep is specified, XFS does not delete empty inode clusters
on the disk (ikeep) - this is the traditional XFS behaviour and keeps them around on disk. ikeep is the traditional XFS
and is still the default for now. Using the noikeep option, behaviour. When noikeep is specified, empty inode clusters
inode clusters are returned to the free space pool. are returned to the free space pool. The default is noikeep.
inode64 inode64
Indicates that XFS is allowed to create inodes at any location Indicates that XFS is allowed to create inodes at any location
......
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