From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: Asdo <asdo@shiftmail.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: small mdadm issue under debian
Date: Thu, 29 Oct 2009 12:04:51 -0600 [thread overview]
Message-ID: <200910291204.51703.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <4AE9D337.30609@shiftmail.org>
On Thu October 29 2009, Asdo wrote:
> Thomas Fjellstrom wrote:
> >> Then reboot to a new kernel and see if it auto assembles.
> >
> > I don't have them auto assemble in initrd/initramfs. Its done later in
> > the mdadm-raid script if I read it correctly. Its also a 1.1 metadata
> > array, so the kernel can't auto assemble it itself.
>
> You probably mean "it can't auto assemble it itself without an
> initramfs"! :-D
Maybe I'm being a little pedantic, but initramfs is a miniature userspace so
it isn't the kernel that is doing the auto assembling ;) just an embedded
mdadm ;)
> I have my root filesystem on a 1.0 metadata raid on 2.6.31 so it
> definitely assembles it...
> For 1.1 I suppose it's the same.
> But it does need to be in the /etc/mdadm/mdadm.conf that is packed in
> the initramfs, so make sure the problem is not that one, try by
> unpacking the initramfs with cpio
>
I don't need it to assemble my array at boot time, the array is used for
media files, not the root partition. I would however like the mdadm-raid
script to be able to assemble the array during boot, which works under
2.6.26, and not under 2.6.29,.30, or .31.
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next prev parent reply other threads:[~2009-10-29 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 7:24 small mdadm issue under debian Thomas Fjellstrom
2009-10-29 7:30 ` Thomas Fjellstrom
2009-10-29 12:26 ` Majed B.
2009-10-29 17:20 ` Thomas Fjellstrom
[not found] ` <4AE9D337.30609@shiftmail.org>
2009-10-29 18:04 ` Thomas Fjellstrom [this message]
2009-11-02 2:03 ` Neil Brown
2009-11-06 21:18 ` Thomas Fjellstrom
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=200910291204.51703.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--cc=asdo@shiftmail.org \
--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).