diff options
authorJosef Sipek <jeffpc@josefsipek.net>2008-04-11 17:11:02 +1000
committerLachlan McIlroy <lachlan@redback.melbourne.sgi.com>2008-04-18 12:18:42 +1000
commitf6e9f28865552bd9d79a9df93cf120436b073223 (patch)
parent033bfb1a65242e0d60e6fc991cd9b3553053d334 (diff)
[XFS] Update XFS documentation for noikeep/ikeep.
Mention how DMAPI affects default for noikeep. Slightly modified since Josef's patch was based on an old xfs.txt prior to Dave's (dgc) checkin which missed going to oss. Signed-off-by: Josef Sipek <jeffpc@josefsipek.net> Signed-off-by: Tim Shimmin <tes@sgi.com>
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/filesystems/xfs.txt b/Documentation/filesystems/xfs.txt
index 10ba81f4be0d..0a1668ba2600 100644
--- a/Documentation/filesystems/xfs.txt
+++ b/Documentation/filesystems/xfs.txt
@@ -59,7 +59,8 @@ When mounting an XFS filesystem, the following options are accepted.
When ikeep is specified, XFS does not delete empty inode clusters
and keeps them around on disk. ikeep is the traditional XFS
behaviour. When noikeep is specified, empty inode clusters
- are returned to the free space pool. The default is noikeep.
+ are returned to the free space pool. The default is noikeep for
+ non-DMAPI mounts, while ikeep is the default when DMAPI is in use.
Indicates that XFS is allowed to create inodes at any location