From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: small mdadm issue under debian
Date: Thu, 29 Oct 2009 01:24:58 -0600 [thread overview]
Message-ID: <200910290124.59090.tfjellstrom@shaw.ca> (raw)
I've been trying to get mdadm to auto assemble my raid array for a while
now, and as I'm trying to test which kernels give me back some performance
(testing 2.6.26 right now), I find that with this kernel, its happily auto
assembling my 1.1 versioned metadata array. 3.6.30 does not, nor does .31 or
.32 for that matter. Same version of mdadm, for some reason, when the
mdadm-raid init script is run, it fails to assemble the raid array I've
specified in mdadm.conf. And again, it automagically works with 2.6.26.
color me confused.
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next reply other threads:[~2009-10-29 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 7:24 Thomas Fjellstrom [this message]
2009-10-29 7:30 ` small mdadm issue under debian 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
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=200910290124.59090.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--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).