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: Tue, 08 Oct 2013 20:36:02 +0200 [thread overview]
Message-ID: <52545092.1040001@arcor.de> (raw)
In-Reply-To: <52541473.4020005@pobox.com>
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. It may require some work on Ubuntu's side.
1 The udev rules for incremental mdadm autoassembly need to be in
place. The upstream rules should be fine. They can normally coexist with
the rules for dmraid.
2 For shutdown, the distro must take care not to kill mdmon before file
systems are unmounted, and to run mdadm --wait-clean after any write
access to file systems is finished.
Martin
next prev parent reply other threads:[~2013-10-08 18:36 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 [this message]
2013-10-10 8:11 ` Brian Candler
2013-10-11 13:03 ` Brian Candler
2013-10-11 18:13 ` Martin Wilck
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=52545092.1040001@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).