From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH 2/2] btrfs-progs: Doc: Add warning for build RAID btrfs on partions from the same device
Date: Fri, 2 Sep 2016 09:41:45 +0800 [thread overview]
Message-ID: <20160902014145.7817-2-quwenruo@cn.fujitsu.com> (raw)
In-Reply-To: <20160902014145.7817-1-quwenruo@cn.fujitsu.com>
Quite a common sense for any RAID-like multi-device setup, just in case.
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
---
Documentation/mkfs.btrfs.asciidoc | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/mkfs.btrfs.asciidoc b/Documentation/mkfs.btrfs.asciidoc
index 846c08f..c291714 100644
--- a/Documentation/mkfs.btrfs.asciidoc
+++ b/Documentation/mkfs.btrfs.asciidoc
@@ -271,6 +271,10 @@ There are the following block group types available:
| RAID6 | 1 | 2 | 3 to N - 2 | 3/any ^(see note3)^
|=============================================================
+WARNING: It's not recommended to build btrfs with RAID0/1/10/5/6 prfiles on
+partitions from the same disk.
+Neither redundancy nor performance will be improved.
+
'Note1:' DUP may exist on more than 1 device if it starts on a single device and
another one is added. Since version 4.5.1, *mkfs.btrfs* will let you create DUP
on multiple devices.
--
2.9.3
next prev parent reply other threads:[~2016-09-02 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 1:41 [PATCH 1/2] btrfs-progs: mkfs: Warn user for minimal RAID5/6 devices setup Qu Wenruo
2016-09-02 1:41 ` Qu Wenruo [this message]
2016-09-06 15:40 ` [PATCH 2/2] btrfs-progs: Doc: Add warning for build RAID btrfs on partions from the same device David Sterba
2016-09-02 1:59 ` [PATCH 1/2] btrfs-progs: mkfs: Warn user for minimal RAID5/6 devices setup Steven Haigh
2016-09-05 16:48 ` David Sterba
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=20160902014145.7817-2-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
/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).