From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 1/3] mkfs.f2fs: fix wrong documentation
Date: Mon, 10 Aug 2015 18:23:46 -0700 [thread overview]
Message-ID: <1439256228-8982-1-git-send-email-jaegeuk@kernel.org> (raw)
The -s should be the number of segments per a section.
Reported-by: Marc Lehmann <schmorp@schmorp.de>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
man/mkfs.f2fs.8 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/man/mkfs.f2fs.8 b/man/mkfs.f2fs.8
index f386ac6..48654aa 100644
--- a/man/mkfs.f2fs.8
+++ b/man/mkfs.f2fs.8
@@ -21,7 +21,7 @@ mkfs.f2fs \- create an F2FS file system
]
[
.B \-s
-.I log-based-#-of-segments-per-section
+.I #-of-segments-per-section
]
[
.B \-z
@@ -60,10 +60,10 @@ Specify the volume label to the partition mounted as F2FS.
Specify the percentage over the volume size for overprovision area. This area
is hidden to users, and utilized by F2FS cleaner. The default percentage is 5%.
.TP
-.BI \-s " log-based-#-of-segments-per-section"
-Specify the log-based number of segments per section. A section consists of
+.BI \-s " #-of-segments-per-section"
+Specify the number of segments per section. A section consists of
multiple consecutive segments, and is the unit of garbage collection.
-The default number is 0, which means one segment is assigned to a section.
+The default number is 1, which means one segment is assigned to a section.
.TP
.BI \-z " #-of-sections-per-zone"
Specify the number of sections per zone. A zone consists of multiple sections.
--
2.1.1
------------------------------------------------------------------------------
next reply other threads:[~2015-08-11 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 1:23 Jaegeuk Kim [this message]
2015-08-11 1:23 ` [PATCH 2/3] mkfs.f2fs: set overprovision size more precisely Jaegeuk Kim
2015-08-11 1:23 ` [PATCH 3/3] mkfs.f2fs: don't need to limit MIN_VOLUME SIZE Jaegeuk Kim
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=1439256228-8982-1-git-send-email-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).