From: "Leslie Rhorer" <lrhorer@satx.rr.com>
To: 'Mark Knecht' <markknecht@gmail.com>,
'Linux-RAID' <linux-raid@vger.kernel.org>
Subject: RE: metadata and / and grub-static
Date: Sun, 4 Apr 2010 21:26:51 -0500 [thread overview]
Message-ID: <2D.29.28131.56A49BB4@cdptpa-omtalb.mail.rr.com> (raw)
In-Reply-To: <u2u5bdc1c8b1004041902l9edc298dg6fb4774aaf8c22a6@mail.gmail.com>
> > keeper ~ # mdadm --create /dev/md0 --level=1 --raid-devices=2
> > /dev/sdb3 /dev/sdc3
> > mdadm: Note: this array has metadata at the start and
> > may not be suitable as a boot device. If you plan to
> > store '/' or '/boot' on this device please ensure that
> > your boot-loader understands md/v1.x metadata, or use
> > --metadata=1.0
> > mdadm: Note: this array has metadata at the start and
> > may not be suitable as a boot device. If you plan to
> > store '/' or '/boot' on this device please ensure that
> > your boot-loader understands md/v1.x metadata, or use
> > --metadata=1.0
As the utility warns you, anything other than 0.9 or 1.0 may have
problems loading as / or /boot, because 1.1 and 1.2 both put the metadata at
the start of the device, in your case a partition.
> > Continue creating array? n
> > mdadm: create aborted.
> > keeper ~ # mdadm --create /dev/md0 --level=1 --raid-devices=2
> > --metadata=1.0 /dev/sdb3 /dev/sdc3
> > mdadm: array /dev/md0 started.
> > keeper ~ # cat /proc/mdstat
> > Personalities : [raid1]
> > md0 : active raid1 sdc3[1] sdb3[0]
> > 31463228 blocks super 1.0 [2/2] [UU]
> > [>....................] resync = 3.9% (1241664/31463228)
> > finish=5.2min speed=95512K/sec
> >
> > unused devices: <none>
> > keeper ~ #
> >
>
> 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.
That said, if the restrictions of a 0.9 superblock are not an issue
for your system, then there is nothing particularly wrong with employing a
0.9 superblock.
> Anyway, the system is running well now.
Unless the restrictions of a 0.9 superblock will cause problems for
you in the future, that's the important thing.
--
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
next prev parent reply other threads:[~2010-04-05 2:26 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 [this message]
2010-04-05 14:15 ` Mark Knecht
2010-04-05 14:55 ` John Robinson
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=2D.29.28131.56A49BB4@cdptpa-omtalb.mail.rr.com \
--to=lrhorer@satx.rr.com \
--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).