linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Accetta <maccetta@laurelnetworks.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID1, hot-swap and boot integrity
Date: Mon, 05 Mar 2007 18:47:57 -0500	[thread overview]
Message-ID: <45ECAC2D.4010404@laurelnetworks.com> (raw)
In-Reply-To: <12721.45EB026B.1040503@zytor.com>

H. Peter Anvin wrote:
> Mike Accetta wrote:
>>
>> I've been considering trying something like having the re-sync algorithm
>> on a whole disk array defer the copy for sector 0 to the very end of the
>> re-sync operation.  Assuming the BIOS makes at least a minimal 
>> consistency
>> check on sector 0 before electing to boot from the drive, this would keep
>> it from selecting a partially re-sync'd drive that was not previously 
>> bootable.
> 
> The only check that it will make is to look for 55 AA at the end of the 
> MBR.
> 
> Note that typically the MBR is not part of any of your MD volumes.

Yes, that is also what I've observed in the case of our BIOS.  I'm still
trying to get our BIOS vendor to confirm that it will fail over to the next
drive in the boot list on a read error of sector 0.  We're contemplating
some GRUB hacking to fail-over to the "other" drive once it is in control
and sees problems.

I wonder if having the MBR typically outside of the array and the relative
newness of partitioned arrays are related?  When I was considering how to
architect the RAID1 layout it seemed like a partitioned array on the
entire disk worked most naturally.
-- 
Mike Accetta

ECI Telecom Ltd.
Data Networking Division (previously Laurel Networks)

  parent reply	other threads:[~2007-03-05 23:47 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
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 [this message]
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=45ECAC2D.4010404@laurelnetworks.com \
    --to=maccetta@laurelnetworks.com \
    --cc=hpa@zytor.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).