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.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
