All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: neilb@cse.unsw.edu.au, linux-raid@vger.kernel.org
Subject: Re: Linux RAID metadata format docs?
Date: Fri, 14 Nov 2003 15:28:47 -0500	[thread overview]
Message-ID: <20031114202846.GA18577@gtf.org> (raw)
In-Reply-To: <20031114193114.GB1080@mea-ext.zmailer.org>

On Fri, Nov 14, 2003 at 09:31:14PM +0200, Matti Aarnio wrote:
> On Fri, Nov 14, 2003 at 01:50:13PM -0500, Jeff Garzik wrote:
> > Do any docs exist, that describe the on-disk md format?
> 
> Not as such.   An  H-file  isn't a document in itself...
> 
> > I'm talking with a vendor that would like to support booting off of 
> > "Linux RAID" (as they call it), from their card's BIOS, which implies
> > the vendor would need to add support for the md format to their BIOS.
> > 
> > 	Jeff
> 
> Problem there is the multitude of partition schemes, and that RAID
> superblocks are inside the partitions...

Yep.  Thought I consider it fairly pointless to support anything but
ms-dos partitions and EFI partitions.  Given limited development
resources, I don't see a huge need for (for example) BSD disklabel
support.


> Nevertheless I would love to be able to boot from _any_ of disks
> in a bootable RAID1 diskset.  I have just experimented with Highpoint's
> RocketRaid 1520, which almost can do that.  It fails if the primary
> disk is offline, but succeeds if secondary is out.
> I also liked their superblock location - very early in disk.
> Negative thing in the HPT BIOS is, that if it detects a fault, it
> wants user input instead of just trying starting disks a bit more 
> persistently, and continuing _soon_ the boot in degraded RAID1 mode
> without any user input.

Yeah, the main point is to be able to root in degraded mode, as well
as regular mode.

	Jeff



  reply	other threads:[~2003-11-14 20:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 18:50 Linux RAID metadata format docs? Jeff Garzik
2003-11-14 19:31 ` Matti Aarnio
2003-11-14 20:28   ` Jeff Garzik [this message]
2003-11-14 21:48   ` Hendrik Visage
2003-11-17  5:55 ` Neil Brown
2003-11-22  1:18   ` Jeff Garzik

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=20031114202846.GA18577@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=neilb@cse.unsw.edu.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.