From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, clm@fb.com
Subject: [PATCH 1/2] btrfs: create degraded-RAID1 chunks
Date: Thu, 28 Apr 2016 11:06:19 +0800 [thread overview]
Message-ID: <1461812780-538-2-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1461812780-538-1-git-send-email-anand.jain@oracle.com>
When RAID1 is degraded, newer chunks should be degraded-RAID1
chunks instead of single chunks.
The bug is because the devs_min for raid1 was wrong it should
be 1, instead of 2.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
fs/btrfs/volumes.c | 38 +++++++++++++++++++++++++++++++++-----
1 file changed, 33 insertions(+), 5 deletions(-)
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index e2b54d546b7c..8b87ed6eb381 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -56,7 +56,7 @@ const struct btrfs_raid_attr btrfs_raid_array[BTRFS_NR_RAID_TYPES] = {
.sub_stripes = 1,
.dev_stripes = 1,
.devs_max = 2,
- .devs_min = 2,
+ .devs_min = 1,
.tolerated_failures = 1,
.devs_increment = 2,
.ncopies = 2,
@@ -4513,6 +4513,7 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
int i;
int j;
int index;
+ int missing_dev = 0;
BUG_ON(!alloc_profile_is_valid(type, 0));
@@ -4627,14 +4628,35 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
sort(devices_info, ndevs, sizeof(struct btrfs_device_info),
btrfs_cmp_device_info, NULL);
- /* round down to number of usable stripes */
- ndevs -= ndevs % devs_increment;
- if (ndevs < devs_increment * sub_stripes || ndevs < devs_min) {
+ /*
+ * For raid1 and raid10; ndevs = devs_min, is less than
+ * (devs_increment * sub_stripes) = x in degraded mode.
+ * For rest of the RAIDs, x is 1
+ */
+ if (ndevs >= (devs_increment * sub_stripes)) {
+ /* round down to number of usable stripes */
+ ndevs -= ndevs % devs_increment;
+ }
+
+ /*
+ * Fix devs_min for RAID10
+ */
+ if (ndevs < devs_min) {
+ /* todo: look for better error reporting */
ret = -ENOSPC;
goto error;
}
+ /*
+ * For RAID1 and RAID10 if there is no sufficient dev for mirror
+ * or stripe, let the chunks be created in degraded mode.
+ * And for rest of RAIDs its fine as (devs_increment * sub_stripes)
+ * is 1.
+ */
+ if (ndevs < (devs_increment * sub_stripes))
+ missing_dev = (devs_increment * sub_stripes) - ndevs;
+
if (devs_max && ndevs > devs_max)
ndevs = devs_max;
/*
@@ -4645,11 +4667,17 @@ static int __btrfs_alloc_chunk(struct btrfs_trans_handle *trans,
num_stripes = ndevs * dev_stripes;
/*
- * this will have to be fixed for RAID1 and RAID10 over
+ * This will have to be fixed for RAID1 and RAID10 over
* more drives
*/
data_stripes = num_stripes / ncopies;
+ if (type & BTRFS_BLOCK_GROUP_RAID1) {
+ if (missing_dev) {
+ /* For RAID1 data_stripes is always 1 rather */
+ data_stripes = num_stripes;
+ }
+ }
if (type & BTRFS_BLOCK_GROUP_RAID5) {
raid_stripe_len = find_raid56_stripe_len(ndevs - 1,
btrfs_super_stripesize(info->super_copy));
--
2.7.0
next prev parent reply other threads:[~2016-04-28 3:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 3:06 [PATCH 0/2] [RFC] btrfs: create degraded-RAID1 chunks Anand Jain
2016-04-28 3:06 ` Anand Jain [this message]
2016-04-29 16:42 ` [PATCH 1/2] " David Sterba
2016-05-02 6:10 ` Anand Jain
2016-05-10 11:00 ` Anand Jain
2016-04-28 3:06 ` [PATCH 2/2] revert: Btrfs: don't consider the missing device when allocating new chunks Anand Jain
2016-04-29 16:37 ` [PATCH 0/2] [RFC] btrfs: create degraded-RAID1 chunks David Sterba
2016-05-02 4:12 ` Anand Jain
2016-05-02 5:30 ` Duncan
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=1461812780-538-2-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--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).