From: Eric Sandeen <sandeen@sandeen.net>
To: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>,
Karel Zak <kzak@redhat.com>
Subject: [PATCH 2/2] xfsprogs: indicate default mount options in xfs.5 manpage
Date: Wed, 11 Jun 2014 15:04:25 -0500 [thread overview]
Message-ID: <5398B649.6020600@sandeen.net> (raw)
In-Reply-To: <5398B5ED.6030703@redhat.com>
Not every pair of mount options indicated which was the
default, so add those.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/man/man5/xfs.5 b/man/man5/xfs.5
index 1729e38..528d99c 100644
--- a/man/man5/xfs.5
+++ b/man/man5/xfs.5
@@ -137,6 +137,8 @@ Enables/disables the use of block layer write barriers for
writes into the journal and for data integrity operations.
This allows for drive level write caching to be enabled, for
devices that support write barriers.
+.sp
+Barriers are enabled by default.
.TP
.BR discard | nodiscard
Enable/disable the issuing of commands to let the block
@@ -147,7 +149,7 @@ machine images, but may have a performance impact.
Note: It is currently recommended that you use the fstrim
application to discard unused blocks rather than the discard
mount option because the performance impact of this option
-is quite severe.
+is quite severe. For this reason, nodiscard is the default.
.TP
.BR grpid | bsdgroups | nogrpid | sysvgroups
These options define what group ID a newly created file
@@ -167,7 +169,7 @@ configured to use it.
When ikeep is specified, XFS does not delete empty inode
clusters and keeps them around on disk. When noikeep is
specified, empty inode clusters are returned to the free
-space pool.
+space pool. noikeep is the default.
.TP
.BR inode32 | inode64
When inode32 is specified, it indicates that XFS limits
@@ -185,6 +187,8 @@ cause problems for some applications that cannot handle
large inode numbers. If applications are in use which do
not handle inode numbers bigger than 32 bits, the inode32
option should be specified.
+.sp
+For kernel v3.7 and later, inode64 is the default.
.TP
.BR largeio | nolargeio
If "nolargeio" is specified, the optimal I/O reported in
@@ -198,7 +202,8 @@ If "largeio" specified, a filesystem that was created with a
in st_blksize. If the filesystem does not have a "swidth"
specified but does specify an "allocsize" then "allocsize"
(in bytes) will be returned instead. Otherwise the behavior
-is the same as if "nolargeio" was specified.
+is the same as if "nolargeio" was specified. nolargeio
+is the default.
.TP
.B logbufs=value
Set the number of in-memory log buffers. Valid numbers
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-11 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 20:02 [PATCH 1/2] xfsprogs: add mount options to xfs.5 manpage Eric Sandeen
2014-06-11 20:04 ` Eric Sandeen [this message]
2014-06-11 23:16 ` [PATCH 2/2] xfsprogs: indicate default mount options in " Dave Chinner
2014-06-16 9:40 ` Christoph Hellwig
2014-06-16 14:29 ` Eric Sandeen
2014-06-11 23:15 ` [PATCH 1/2] xfsprogs: add mount options to " Dave Chinner
2014-06-16 9:39 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5398B649.6020600@sandeen.net \
--to=sandeen@sandeen.net \
--cc=kzak@redhat.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox