From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: <dsterba@suse.cz>
Cc: <linux-btrfs@vger.kernel.org>, <takeuchi_satoru@jp.fujitsu.com>,
Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Subject: [PATCH v3] btrfs-progs: Documentation: add T/P/E description for resize cmd
Date: Tue, 30 Dec 2014 09:52:17 +0800 [thread overview]
Message-ID: <1419904337-9945-1-git-send-email-guihc.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <20141229160712.GK6490@twin.jikos.cz>
Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
---
changelog
v1->v2:
s/\'E\'(EiB)/or \'E\'(EiB)/ as suggested by Satoru, thanks.
v2->v3:
replace confusing format 'K'(KiB) etc. Thanks, David.
---
Documentation/btrfs-filesystem.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/btrfs-filesystem.txt b/Documentation/btrfs-filesystem.txt
index a8f2972..96c4420 100644
--- a/Documentation/btrfs-filesystem.txt
+++ b/Documentation/btrfs-filesystem.txt
@@ -102,8 +102,9 @@ If the prefix + or - is present the size is increased or decreased
by the quantity <size>.
If no units are specified, the unit of the <size> parameter defaults to
bytes. Optionally, the size parameter may be suffixed by one of the following
-units designators: \'K\', \'M', or \'G', kilobytes, megabytes, or gigabytes,
-respectively.
+units designators: \'K\', \'M\', \'G\', \'T\', \'P\', or \'E\', which represent
+KiB, MiB, GiB, TiB, PiB, or EiB, respectively.
+
+
If \'max' is passed, the filesystem will occupy all available space on the
device devid.
--
1.8.1.4
next prev parent reply other threads:[~2014-12-30 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 2:01 [PATCH] btrfs-progs: Documentation: add T/P/E description for resize cmd Gui Hecheng
2014-12-22 3:20 ` Satoru Takeuchi
2014-12-22 7:22 ` [PATCH v2] " Gui Hecheng
2014-12-29 16:07 ` David Sterba
2014-12-30 1:23 ` Gui Hecheng
2014-12-30 1:52 ` Gui Hecheng [this message]
2015-01-02 3:27 ` [PATCH v3] " Chris Murphy
2015-01-02 16:12 ` David Sterba
2015-01-02 16:21 ` David Sterba
2015-01-05 1:42 ` Gui Hecheng
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=1419904337-9945-1-git-send-email-guihc.fnst@cn.fujitsu.com \
--to=guihc.fnst@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=takeuchi_satoru@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).