From: John Robinson <john.robinson@anonymous.org.uk>
To: Martin Cracauer <cracauer@cons.org>
Cc: Leslie Rhorer <lrhorer@satx.rr.com>, linux-raid@vger.kernel.org
Subject: Re: Superblock V 1.2
Date: Sun, 07 Nov 2010 21:39:03 +0000 [thread overview]
Message-ID: <4CD71C77.4030400@anonymous.org.uk> (raw)
In-Reply-To: <20101107210852.GA77472@cons.org>
On 07/11/2010 21:08, Martin Cracauer wrote:
> Thanks, Leslie,
>
> Leslie Rhorer wrote on Sun, Nov 07, 2010 at 03:03:39PM -0600:
>>
>>> Can I read that array if I ever connect the machine to an older
>>> kernel/mdadm?
>>
>> That depends on just how old. The new superblocks have been
>> supported for quite some time. Worst case you will need to upgrade the old
>> kernel to a newer one.
>
> Is mdadm actually involved? If I have a new enough kernel but an old
> mdadm, will the kernel code alone be enough to start the array?
>
> I guess it should since it can start the arrays at boot time with no
> mdadm involved.
That's the other difference between 0.90 and 1.x metadata. In-kernel
auto-assembly is only available for 0.90, and Neil Brown has made it
clear that there will never be in-kernel auto-assembly for 1.x, and
explained at length why. You need mdadm to start 1.x arrays, in your
initrd if your root filesystem is on such an array. All modern distros
create suitable initrds automatically. We are moving towards having
array assembly handled by udev invoking mdadm as devices are discovered.
Cheers,
John.
next prev parent reply other threads:[~2010-11-07 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 19:15 Superblock V 1.2 Martin Cracauer
2010-11-07 21:03 ` Leslie Rhorer
2010-11-07 21:08 ` Martin Cracauer
2010-11-07 21:39 ` John Robinson [this message]
2010-11-09 16:35 ` Martin Cracauer
2010-11-09 17:08 ` John Robinson
2010-11-15 1:11 ` Neil Brown
2010-11-15 16:16 ` Martin Cracauer
2010-11-15 19:47 ` Neil Brown
2010-11-15 19:52 ` Martin Cracauer
2010-11-15 20:11 ` Neil Brown
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=4CD71C77.4030400@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=cracauer@cons.org \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.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).