From: "Jon Nelson" <jnelson-linux-raid@jamponi.net>
To: Neil Brown <neilb@suse.de>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: behavior different from mdadm 2.6.4 and 3.0?
Date: Mon, 15 Dec 2008 20:35:08 -0600 [thread overview]
Message-ID: <cccedfc60812151835xb3a1442u4f344c26df075888@mail.gmail.com> (raw)
In-Reply-To: <18759.1035.627538.450310@notabene.brown>
On Mon, Dec 15, 2008 at 7:27 PM, Neil Brown
> That's the problem then.
> The array was started from initrd and any mdadm/map that was created
> would have got lost.
> Now it needs one to continue with assembly and cannot find one.
> I'll have to get it to do the "-Ir" thing automagically if mdadm/map
> does not exist.
>> Does that help?
>
> So: yes it does - thanks.
Awesome!
> I've got some coding to do ;-)
I'm sorry to be causing you more work.
--
Jon
prev parent reply other threads:[~2008-12-16 2:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 14:54 behavior different from mdadm 2.6.4 and 3.0? Jon Nelson
2008-12-15 21:11 ` Neil Brown
2008-12-15 21:35 ` Jon Nelson
2008-12-16 1:27 ` Neil Brown
2008-12-16 2:35 ` Jon Nelson [this message]
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=cccedfc60812151835xb3a1442u4f344c26df075888@mail.gmail.com \
--to=jnelson-linux-raid@jamponi.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).