From: Martin Wilck <mwilck@arcor.de>
To: Francis Moreau <francis.moro@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: How does md(adm) work with fake-raid ?
Date: Fri, 19 Jul 2013 20:52:31 +0200 [thread overview]
Message-ID: <51E98AEF.5060206@arcor.de> (raw)
In-Reply-To: <CAC9WiBiup8RfusZo51DjAsTOLyr1F-LxgGGCWRCakYURskz7rA@mail.gmail.com>
> Yes, but my question is about how md cooperate with the BIOS in this case ?
Not sure what you mean. When Linux runs, with or without MD, no BIOS
code is ever executed.
The only way of communication between BIOS and MD is the meta data. When
you create an array in your BIOS setup tool, The BIOS will write the
meta data. MD will read it, and when it's done, it will re-write it
(usually unchanged, unless a disk failure occurs, but there are some
fields such as sequential numbers and time stamps that change every time
the meta data is written). The BIOS will read this back the next time
your system boots.
> Are there any procedures described out there that I could follow to
> test MD DFF ?
Not really. Play around, test various RAID levels etc, whatever your
fake RAID supports. If you have a Linux or Windows driver for your fake
raid, check if it correctly detects your setup after MD had control.
Note that RAID arrays *created* by MD (with mdadm -C) will most probably
not be accepted by the BIOS (it will consider them "foreign
configurations" and not import them).
Martin
next prev parent reply other threads:[~2013-07-19 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 20:37 How does md(adm) work with fake-raid ? Francis Moreau
2013-07-18 22:03 ` Martin Wilck
2013-07-18 23:35 ` Dmitrijs Ledkovs
2013-07-19 15:58 ` Jiang, Dave
2013-07-19 18:58 ` Martin Wilck
[not found] ` <51E85949.2020107@gmail.com>
2013-07-19 7:02 ` Francis Moreau
[not found] ` <51E86613.9050505@arcor.de>
2013-07-19 7:08 ` Francis Moreau
2013-07-19 18:52 ` Martin Wilck [this message]
2013-07-21 13:41 ` Francis Moreau
2013-07-21 17:10 ` 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=51E98AEF.5060206@arcor.de \
--to=mwilck@arcor.de \
--cc=francis.moro@gmail.com \
--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 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.