linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Gabor Gombas <gombasg@sztaki.hu>
Cc: Mike Accetta <maccetta@laurelnetworks.com>, linux-raid@vger.kernel.org
Subject: Re: RAID1, hot-swap and boot integrity
Date: Fri, 02 Mar 2007 15:57:14 -0500	[thread overview]
Message-ID: <45E88FAA.5020106@tmr.com> (raw)
In-Reply-To: <20070302161004.GE31010@boogie.lpds.sztaki.hu>

Gabor Gombas wrote:
> On Fri, Mar 02, 2007 at 09:04:40AM -0500, Mike Accetta wrote:
>
>   
>> Thoughts or other suggestions anyone?
>>     
>
> This is a case where a very small /boot partition is still a very good
> idea... 50-100MB is a good choice (some initramfs generators require
> quite a bit of space under /boot while generating the initramfs image
> esp. if you use distro-provided "contains-everything-and-the-kitchen-sink"
> kernels, so it is not wise to make /boot _too_ small).
>   
You are exactly right on that! Some (many) BIOS implementations will 
read the boot sector off the drive, and if there is no error will run 
the boot sector.
> But if you do not want /boot to be separate a moderately sized root
> partition is equally good. What you want to avoid is the "whole disk is
> a single partition/file system" kind of setup.
>
>   
Actually, the solution is moderately simple, install the replacement 
drive, create the partitions, and **don't mark the boot partition 
active** until the copy is complete. The BIOS will boot from the 1st 
active partition it finds (again, in sane cases).

I never have anything changing in /boot in normal operation, so I admit 
to using dd to do a copy with the array stopped. No particular reason to 
think it works better than just a rebuild. After the partition is valid 
I set the active flag in the partition.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  reply	other threads:[~2007-03-02 20:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 14:04 RAID1, hot-swap and boot integrity Mike Accetta
2007-03-02 15:40 ` Justin Piszcz
2007-03-02 16:02   ` Gabor Gombas
2007-03-02 16:10 ` Gabor Gombas
2007-03-02 20:57   ` Bill Davidsen [this message]
2007-03-04 17:31 ` H. Peter Anvin
     [not found] ` <9782.20070302161004.GE31010@boogie.lpds.sztaki.hu>
2007-03-05 23:32   ` Mike Accetta
2007-03-06 10:01     ` Gabor Gombas
     [not found] ` <12470.45E88FAA.5020106@tmr.com>
2007-03-05 23:38   ` Mike Accetta
2007-03-06 23:17     ` Bill Davidsen
2007-03-07 20:48     ` H. Peter Anvin
     [not found] ` <12721.45EB026B.1040503@zytor.com>
2007-03-05 23:47   ` Mike Accetta
2007-03-05 23:55     ` H. Peter Anvin
2007-03-06 23:18       ` Bill Davidsen

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=45E88FAA.5020106@tmr.com \
    --to=davidsen@tmr.com \
    --cc=gombasg@sztaki.hu \
    --cc=linux-raid@vger.kernel.org \
    --cc=maccetta@laurelnetworks.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).