From: Martin Wilck <mwilck@arcor.de>
To: linux-raid@vger.kernel.org
Cc: mwilck@arcor.de
Subject: DDF RAID 10 with md?
Date: Mon, 10 Dec 2012 21:23:35 +0100 [thread overview]
Message-ID: <50C644C7.3060502@arcor.de> (raw)
In-Reply-To: <1354919941-12070-1-git-send-email-mwilck@arcor.de>
I wrote
> PS: These patches fix RAID1. I noticed that there are more severe problems
> when I create a RAID 10 in the BIOS. I'll try to fix that, too.
I've digged a little further and from what I understand, the RAID10
concept in DDF ("DDF_2SPANNED" is what by BIOS creates) is incompatible
with that of MD RAID.
So I guess there is no easy solution, short of implementing an entirely
new RAID mapping in md.
Another possibility might be to setup the "spanning" block map of the
DDF secondary RAID using dm. There would be some minor problems to
overcome first though:
1 - Currently, if I configure RAID10 in the BIOS, md will only
configure the first of the two basic RAID1 arrays.
2 - When md is stopped and writes back the meta data, it will change
the seq number only on the first basic arrays, thus corrupting the meta
data of the RAID set.
I'd suggest that md should bail out if a DDF secondary RAID level is
encountered, knowing that this mapping is currently unsupported. That'd
be certainly better than corrupting the metadata.
Regards
Martin
next prev parent reply other threads:[~2012-12-10 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 22:38 Fixes for DDF with LSI BIOS RAID mwilck
2012-12-07 22:38 ` [PATCH 1/3] DDF: cleanly save the secondary DDF structure mwilck
2012-12-07 22:39 ` [PATCH 2/3] DDF: use existing locations for primary and " mwilck
2012-12-07 22:39 ` [PATCH 3/3] DDF: increase seq number when writing meta data mwilck
2012-12-10 20:23 ` Martin Wilck [this message]
2013-01-17 20:41 ` Fixes for DDF with LSI BIOS RAID Martin Wilck
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=50C644C7.3060502@arcor.de \
--to=mwilck@arcor.de \
--cc=linux-raid@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).