From: "H. Peter Anvin" <hpa@zytor.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Chris Mason <chris.mason@fusionio.com>,
"Chris L. Mason" <clmason@fusionio.com>,
Marios Titas <redneb8888@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Feature request: true RAID-1 mode
Date: Mon, 02 Jul 2012 08:59:19 -0700 [thread overview]
Message-ID: <4FF1C557.2040705@zytor.com> (raw)
In-Reply-To: <4FE8EDA1.5090004@zytor.com>
On 06/25/2012 04:00 PM, H. Peter Anvin wrote:
>
> I am aware of that, and it is not a problem... the one-device
> bootloader can find out *which* disk it is talking to by comparing
> uuids, and the btrfs data structures will tell it how to find the data
> on that specific disk. It does of course mean the bootloader needs to
> be aware of the multidisk nature of btrfs, but that isn't a problem in
> itself.
>
So, also, let me address the question why we should care about a
one-device bootloader. It is quite common, especially in fileservers,
for a subset of the boot devices to be inaccessible by the firmware, due
to bugs, boot time concerns (spinning up all the media in the firmware
is SLOW) or just plain lack of support of plug-in cards. As such, the
reliable thing to do is to make sure that any disk being seen is enough
to bring up the system; since this is such a small amount of data with
modern standards, there is just no reason to do anything less robust.
Once the kernel comes up it has all the device drivers, of course.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2012-07-02 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 16:27 Feature request: true RAID-1 mode H. Peter Anvin
2012-06-21 0:35 ` Marios Titas
2012-06-21 0:50 ` Chris Mason
2012-06-21 1:34 ` H. Peter Anvin
2012-06-25 15:21 ` Chris Mason
2012-06-25 17:46 ` H. Peter Anvin
2012-06-25 22:34 ` Gareth Pye
[not found] ` <CA+WRLO87LvTrRJRMNwYQ3SwmZWF7WzO_FDi1=jqt1kwX=YSnWQ@mail.gmail.com>
2012-06-25 22:37 ` H. Peter Anvin
2012-06-25 22:46 ` Gareth Pye
2012-06-25 22:54 ` Hugo Mills
2012-06-25 23:00 ` H. Peter Anvin
2012-07-02 15:59 ` H. Peter Anvin [this message]
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=4FF1C557.2040705@zytor.com \
--to=hpa@zytor.com \
--cc=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=redneb8888@gmail.com \
/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).