linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Mark Knecht <markknecht@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: metadata and / and grub-static
Date: Mon, 05 Apr 2010 15:55:32 +0100	[thread overview]
Message-ID: <4BB9F9E4.2060802@anonymous.org.uk> (raw)
In-Reply-To: <r2m5bdc1c8b1004050715q6db273f9o8d1c291a43ebd308@mail.gmail.com>

On 05/04/2010 15:15, Mark Knecht wrote:
> On Sun, Apr 4, 2010 at 7:26 PM, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
> <SNIP>
>>> Answering self - putting / on RAID1 only seems to work using
>>> --metadata=0.90. Tried it with higher versions and had no luck.
>>        One may most certainly run a RAID1 / or /boot (or both) using other
>> than 0.9 metadata.  I'm running two servers with / on a 1.02 superblock and
>> /boot on a 1.0 superblock, booting with grub 0.97.
> 
> Are you using an initrd? I could not make it work above 0.90 without
> going that way which I didn't want to do.

Yes, the kernel will only auto-assemble arrays with 0.90 metadata, and 
Neil Brown has stated several times that there never will be support for 
auto-assembling anything else in the kernel.

You can still have your /boot with 1.0 metadata using grub 0.97 (or even 
LILO) and your root with any metadata but you will need an initrd 
containing mdadm with which to assemble your arrays before attempting to 
mount the root filesystem.

But if you're determined to avoid an initrd, you're stuck with 0.90 
metadata for your root filesystem. This probably isn't much of a 
limitation since you can still have a 27-drive RAID-6 array of 2TB discs 
with write-intent bitmap if you want. (It might even be 28 discs.) And 
if you had an array as funky as that, you'd probably want to run LVM 
over the top of it, so you'd need an initrd anyway, so you'd be able to 
use 1.x metadata :-)

Since most distros ship highly modular kernels, their installers and 
tools all build initrds, so for most people, needing an initrd is not an 
issue.

Anyway, a quick summary:
* with grub 0.97 or LILO, /boot (more generally, wherever your vmlinuz 
lives) must be RAID-1 on 0.90 or 1.0 metadata, and the members must be 
on drives the BIOS will boot from, usually sda/b/c
* without an initrd, / must be on 0.90 metadata but any RAID level or 
disc location (that the kernel doesn't need extra modules for) is fine
* and combining these, if you're running grub 0.97 (or LILO) and don't 
want a separate /boot array (or keep your vmlinuz in the root) and don't 
want to use an initrd, you're restricted to having your root filesystem 
on RAID-1 on 0.90 metadata on drives the BIOS will boot from

Cheers,

John.


  reply	other threads:[~2010-04-05 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 19:34 metadata and / and grub-static Mark Knecht
2010-04-05  2:02 ` Mark Knecht
2010-04-05  2:26   ` Leslie Rhorer
2010-04-05 14:15     ` Mark Knecht
2010-04-05 14:55       ` John Robinson [this message]
2010-04-05 15:52         ` Mark Knecht
2010-04-05 16:31           ` John Robinson
2010-04-05 16:44             ` Mark Knecht

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=4BB9F9E4.2060802@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=markknecht@gmail.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).