From: Matt Domsch <Matt_Domsch@dell.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] embryonic RAID class
Date: Thu, 18 Aug 2005 07:44:06 -0500 [thread overview]
Message-ID: <20050818124406.GA13687@lists.us.dell.com> (raw)
In-Reply-To: <1124318725.5221.12.camel@mulgrave>
On Wed, Aug 17, 2005 at 06:45:25PM -0400, James Bottomley wrote:
> > Add hotspare-0, hotspare-1 ... to the list?
>
> Yes ... I only have two disks though, so I've reached the limit of what
> I can do with my current fusion setup. The whole of the component
> display has to be reworked anyway (I only provide add, but obviously
> delete should be allowed as well as component type). I'll add it to the
> list. Probably we also need a component state model as well (and
> perhaps spare would be one of the states).
Different controllers have different hot spare capabilities. Some hot
spares are global to the whole array and can fill in if any disk
fails. Others are tied to either a group of logical volumes, or to a
single logical volume. The first and third associations are easy, the
second association will require a new group concept.
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2005-08-18 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 20:25 [RFC] embryonic RAID class Salyzyn, Mark
2005-08-17 22:45 ` James Bottomley
2005-08-18 12:44 ` Matt Domsch [this message]
2005-08-18 17:16 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 23:27 James Bottomley
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=20050818124406.GA13687@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.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).