From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: linux-raid@vger.kernel.org
Cc: Eric Wood <eric@interplas.com>,
"Cress, Andrew R" <andrew.r.cress@intel.com>
Subject: Re: Converting a non-RAID RedHat System to run on Software RAID
Date: Wed, 10 Sep 2003 09:18:49 -0400 [thread overview]
Message-ID: <20030910131849.GA5267@ti19> (raw)
In-Reply-To: <E5DA6395B8F9614EB7A784D628184B200D9A56@hdsmsx402.hd.intel.com>
On Tue, Sep 09, 2003 at 02:37:18PM -0400, Cress, Andrew R wrote:
> The instructions are oriented to lilo, but the grub equivalent is
> scripted in files/mdevt script:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/scsirastools/s
> csirastools/files/mdevt?rev=HEAD&content-type=text/plain
A word of caution:
One miserable consequence of using GRUB on RAID1 is inadvertent corruption
of (a small part of the) RAID-1 /boot partition. Since grub (at least
in Red Hat Rawhide) doesn't grok MD, if one sets up a RAID-1 /boot
partitiion, say
/dev/md1 -> (/dev/sda1,dev/sdb1),
then modifications made at the grub prompt modify the filesystem and
desynchronizes the RAID1 set. [It seems that simply using 'e' to edit the
kernel args has this effect, though I haven't verified it myself.] We see
this corruption in MD5 variation in our nightly integrity-verification
cron job.
Grub has a --read-only option when running the grub shell from Linux;
I haven't yet found the time to delve into the code to see whether it
is simple to do the same in the stage2 loader, or whether the read-only
behavior is purely a function of the device open() when running the grub
shell.
Trivial workaround is to resync the second drive in the rc scripts;
for the typical 50-100MB /boot partition, this takes only a few seconds.
Regards,
Bill Rugolsky
next prev parent reply other threads:[~2003-09-10 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 18:37 Converting a non-RAID RedHat System to run on Software RAID Cress, Andrew R
2003-09-10 13:18 ` Bill Rugolsky Jr. [this message]
2003-09-11 12:21 ` Eric Wood
-- strict thread matches above, loose matches on Subject: below --
2003-09-09 18:17 Eric Wood
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=20030910131849.GA5267@ti19 \
--to=brugolsky@telemetry-investments.com \
--cc=andrew.r.cress@intel.com \
--cc=eric@interplas.com \
--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).