From: Martin Wilck <mwilck@arcor.de>
To: Brian Candler <b.candler@pobox.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Using mdadm instead of dmraid for BIOS-RAID root volume
Date: Fri, 11 Oct 2013 20:13:21 +0200 [thread overview]
Message-ID: <52583FC1.1070107@arcor.de> (raw)
In-Reply-To: <5257F706.8050708@pobox.com>
On 10/11/2013 03:03 PM, Brian Candler wrote:
> On 08/10/2013 19:36, Martin Wilck wrote:
>> On 10/08/2013 04:19 PM, Brian Candler wrote:
>>> > Anyway, I'm not so worried about having broken this machine, as it
>>> needed a reinstall anyway, but I do wonder what would have been the
>>> correct way to get mdraid instead of dmraid at boot time for this root
>>> volume?
>>>
>>> After some more searching, it looks like the udev rules were nobbled to
>>> disable this in
>>> https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1030292
>>>
>>> A possible way to re-enable is here:
>>> https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1054948/comments/9
>>>
>>> I'm a bit concerned about the issues around clean shutdown, and hence
>>> whether is really production-ready yet.
>> In general, this works. I have seen it work with CentOS, Fedora, and
>> various SUSE distributions.
> FWIW, I found problems on stock CentOS 6.4.
>
> I had created two RAID volumes within the BIOS:
> "BOOT" (4GB)
> "LVM" (rest of disk)
>
> These are correctly detected and come up as md0 (container), md125
> (BOOT), md126 (LVM). In a previous install using Debian I had set these
> up as ext4 and LVM respectively.
>
> In the CentOS graphical installer, they are shown as:
>
> V Hard Drives
> md125 4096 ext4
> md126 902246 vg Physical volume (LVM)
>
> (md0 is not shown)
>
> Problem: if I double-click on md125, or select md125 and click Edit...,
> nothing happens. Therefore I cannot mark it as being used for the /boot
> filesystem.
>
> However, if I double-click on md126, it correctly pops up "You cannot
> edit this drive: This device is part of the LVM volume group 'vg'."
>
> Then if I delete all the logical volumes, and the volume group, I
> expected to be able to edit md126 - but I can't. Again, just nothing
> happens when I double-click on it. I can neither partition it, nor
> change it to ext4 and mount it.
>
> So it looks like there's work remaining to make this usable in CentOS too.
Maybe, but your setup is pretty unusual. These MD arrays are "disks" for
the installer, and thus would need to be partitioned. I believe it would
work better that way. I have never tried an LVM PV on a whole disk.
Martin
>
> Regards,
>
> Brian.
>
next prev parent reply other threads:[~2013-10-11 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 12:17 Using mdadm instead of dmraid for BIOS-RAID root volume Brian Candler
2013-10-08 14:19 ` Brian Candler
2013-10-08 18:36 ` Martin Wilck
2013-10-10 8:11 ` Brian Candler
2013-10-11 13:03 ` Brian Candler
2013-10-11 18:13 ` Martin Wilck [this message]
2013-10-11 19:49 ` Brian Candler
2013-10-13 16:44 ` Martin Wilck
2013-10-13 18:12 ` Brian Candler
2013-10-08 14:37 ` Jes Sorensen
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=52583FC1.1070107@arcor.de \
--to=mwilck@arcor.de \
--cc=b.candler@pobox.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 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).