From: Lars Marowsky-Bree <lmb@suse.de>
To: NeilBrown <neilb@suse.de>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 000 of 7] md: Introduction - raid5 reshape mark-2
Date: Tue, 24 Jan 2006 10:23:03 +0100 [thread overview]
Message-ID: <20060124092303.GD22870@marowsky-bree.de> (raw)
In-Reply-To: <20060124112626.4447.patches@notabene>
On 2006-01-24T11:40:47, NeilBrown <neilb@suse.de> wrote:
> I am expecting that I will ultimately support online conversion of
> raid5 to raid6 with only one extra device. This process is not
> (efficiently) checkpointable and so will be at-your-risk.
So the best way to go about that, if one wants to keep that option open
w/o that risk, would be to not create a raid5 in the first place, but a
raid6 with one disk missing?
Maybe even have mdadm default to that - as long as just one parity disk
is missing, no slowdown should happen, right?
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Lars Marowsky-Bree <lmb@suse.de>
To: NeilBrown <neilb@suse.de>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 000 of 7] md: Introduction - raid5 reshape mark-2
Date: Tue, 24 Jan 2006 10:23:03 +0100 [thread overview]
Message-ID: <20060124092303.GD22870@marowsky-bree.de> (raw)
In-Reply-To: <20060124112626.4447.patches@notabene>
On 2006-01-24T11:40:47, NeilBrown <neilb@suse.de> wrote:
> I am expecting that I will ultimately support online conversion of
> raid5 to raid6 with only one extra device. This process is not
> (efficiently) checkpointable and so will be at-your-risk.
So the best way to go about that, if one wants to keep that option open
w/o that risk, would be to not create a raid5 in the first place, but a
raid6 with one disk missing?
Maybe even have mdadm default to that - as long as just one parity disk
is missing, no slowdown should happen, right?
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next prev parent reply other threads:[~2006-01-24 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 0:40 [PATCH 000 of 7] md: Introduction - raid5 reshape mark-2 NeilBrown
2006-01-24 0:40 ` [PATCH 001 of 7] md: Split disks array out of raid5 conf structure so it is easier to grow NeilBrown
2006-01-24 0:40 ` [PATCH 002 of 7] md: Allow stripes to be expanded in preparation for expanding an array NeilBrown
2006-01-24 0:41 ` [PATCH 003 of 7] md: Infrastructure to allow normal IO to continue while array is expanding NeilBrown
2006-01-24 0:41 ` [PATCH 004 of 7] md: Core of raid5 resize process NeilBrown
2006-01-24 0:41 ` [PATCH 005 of 7] md: Final stages of raid5 expand code NeilBrown
2006-01-24 0:41 ` [PATCH 006 of 7] md: Checkpoint and allow restart of raid5 reshape NeilBrown
2006-01-27 12:37 ` Molle Bestefich
2006-01-24 0:41 ` [PATCH 007 of 7] md: Only checkpoint expansion progress occasionally NeilBrown
2006-01-24 9:23 ` Lars Marowsky-Bree [this message]
2006-01-24 9:23 ` [PATCH 000 of 7] md: Introduction - raid5 reshape mark-2 Lars Marowsky-Bree
2006-01-24 9:32 ` Neil Brown
2006-02-07 17:13 ` Henrik Holst
2006-02-09 3:32 ` Neil Brown
2006-02-09 6:35 ` Kernels and MD versions (was: md: Introduction - raid5 reshape mark-2) Patrik Jonsson
2006-02-09 18:07 ` Mr. James W. Laferriere
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=20060124092303.GD22870@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.