From: Tommy Apel Hansen <tommyapeldk@gmail.com>
To: Mark Knecht <markknecht@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Any risk switching mdadm to static?
Date: Wed, 26 Dec 2012 20:32:48 +0100 [thread overview]
Message-ID: <1356550368.3016.3.camel@workstation-home> (raw)
In-Reply-To: <CAK2H+ee_u3bc7ZgN9z9CJbuSN+8HVyeTLwRaCn5hCP1fB3w8NQ@mail.gmail.com>
Hello Mark,
if you use genkernel initramfs you shouldn't have any problems, just
make sure you mdadm.conf is up to date when you ask genkernel to make
the initramfs, what the initramfs does it to boot your system into a
ramdisk and then initialize everything from there before pivoting into
the real OS, worst case you'll end up in a rescure shell where you can
start up the md's and then ask the system to use them after you exit the
shell.
/Tommy
On Wed, 2012-12-26 at 09:57 -0800, Mark Knecht wrote:
> Hi,
> I run a bunch of home Gentoo systems most of which use mdadm,
> currently version 3.1.4. I do not currently use initramfs's on any of
> these systems but figure it's time for me to crawl out of my dark ages
> swamp and try to become more enlightened.
>
> QUESTION: Is there an significant risk that a normal Gentoo system
> of the stable variety (I.e. - not ~amd64) would encounter any problems
> booting if mdadm-3.1.4 was rebuilt using the static flag? If it
> matters most of my RAIDs are metadata-0.9. One is 1.2.
>
> If I did encounter a problem and couldn't boot is there a way to recover?
>
> Please note, I'm not asking right now about using mdadm from within
> an initramfs. I'm only trying to ensure that if I rebuild mdadm with
> the static flag the current system is still likely to boot OK.
>
> Folks on the Gentoo list say they didn't have any problems
> switching, but they switched a long, long time ago so I'm just trying
> to be extra sure.
>
> Thanks in advance,
> Mark
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-12-26 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 17:57 Any risk switching mdadm to static? Mark Knecht
2012-12-26 19:02 ` Phil Turmel
[not found] ` <CAK2H+ecQpTtipdPWQmVj2gCZ6FPzeXfx5bj8y4asVdhf1CTkfA@mail.gmail.com>
2012-12-26 19:53 ` Phil Turmel
2012-12-26 19:32 ` Tommy Apel Hansen [this message]
[not found] ` <CAK2H+efpHB-Okn_PaitAKmLPKwmn1kNZzJpEvM-BW7fWWwrZVw@mail.gmail.com>
2012-12-26 19:55 ` Tommy Apel Hansen
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=1356550368.3016.3.camel@workstation-home \
--to=tommyapeldk@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@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).