From: Phil Turmel <philip@turmel.org>
To: "Rainer Fügenstein" <rfu@oudeis.org>
Cc: John Robinson <john.robinson@anonymous.org.uk>,
linux-raid@vger.kernel.org
Subject: Re: 4x3TB raid5 - no autodetect
Date: Mon, 22 Oct 2012 12:14:45 -0400 [thread overview]
Message-ID: <508570F5.9090202@turmel.org> (raw)
In-Reply-To: <123699751.20121022175600@oudeis.org>
On 10/22/2012 11:56 AM, Rainer Fügenstein wrote:
>
> JR> In-kernel auto-assembly is only supported for metadata 0.90, and even
> JR> then the feature is deprecated. If you have your root filesystem on a md
> JR> array, use an initrd with mdadm in it to start it.
>
> if I understand it correctly, metadata 0.90 is not supporting drives >
> 2TB?
v0.9 supports drives to 4T, but there was a bug in several released
kernels that triggered above 2T. There are also unsolvable
misidentification issues for partitioned drives where the last partition
can be confused with the whole disk.
> will in-kernel auto-assembly be supported sometimes in the future?
> this was quite a useful feature.
I'm sure Neil will pipe up if necessary, but he has been adamantly
against extending the in-kernel autoassembly code in any way. Auto-
assembly is also incompatible with GPT partitions.
You should use v1.0 for mirrored boot partitions, and v1.2 for all other
arrays. And use an initramfs.
I, too, squirmed when faced with the need to set up an initramfs, as I
was quite comfortable with my legacy configuration. I'm glad I got over it.
HTH,
Phil
--
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
prev parent reply other threads:[~2012-10-22 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 13:55 4x3TB raid5 - no autodetect Rainer Fügenstein
2012-10-22 14:11 ` John Robinson
2012-10-22 15:56 ` Re[2]: " Rainer Fügenstein
2012-10-22 16:14 ` Phil Turmel [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=508570F5.9090202@turmel.org \
--to=philip@turmel.org \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=rfu@oudeis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.