From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: ATARAID userspace configuration tool
Date: Wed, 11 Feb 2004 07:18:26 -0700 [thread overview]
Message-ID: <402A39B2.1010207@backtobasicsmgmt.com> (raw)
In-Reply-To: <1076499258.5253.1.camel@leto.cs.pocnet.net>
Christophe Saout wrote:
> Aren't the disks the ATARAID is made of usually on the same controller?
> Then you only have to scan that one.
Yes, that would be a simple optimization for this case. I was
envisioning the future tools to handle existing MD and LVM autodetection
and that would require looking at all potential block devices.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: ATARAID userspace configuration tool
Date: Wed, 11 Feb 2004 07:18:26 -0700 [thread overview]
Message-ID: <402A39B2.1010207@backtobasicsmgmt.com> (raw)
In-Reply-To: <1076499258.5253.1.camel@leto.cs.pocnet.net>
Christophe Saout wrote:
> Aren't the disks the ATARAID is made of usually on the same controller?
> Then you only have to scan that one.
Yes, that would be a simple optimization for this case. I was
envisioning the future tools to handle existing MD and LVM autodetection
and that would require looking at all potential block devices.
next prev parent reply other threads:[~2004-02-11 14:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 14:18 ATARAID userspace configuration tool Thomas Horsten
2004-02-10 14:18 ` Thomas Horsten
2004-02-10 14:51 ` Matt Domsch
2004-02-10 14:58 ` Christophe Saout
2004-02-10 18:26 ` Kevin P. Fleming
2004-02-10 18:26 ` Kevin P. Fleming
2004-02-10 19:18 ` Christophe Saout
2004-02-10 19:24 ` Kevin P. Fleming
2004-02-10 19:24 ` Kevin P. Fleming
2004-02-11 1:35 ` Greg KH
2004-02-11 1:45 ` Kevin P. Fleming
2004-02-11 1:45 ` Kevin P. Fleming
2004-02-11 11:34 ` Christophe Saout
2004-02-11 14:18 ` Kevin P. Fleming [this message]
2004-02-11 14:18 ` Kevin P. Fleming
2004-02-11 19:48 ` Christophe Saout
2004-02-10 17:38 ` Jeff Garzik
2004-02-10 17:47 ` Thomas Horsten
2004-02-10 17:47 ` Thomas Horsten
2004-02-10 18:44 ` Jeff Garzik
2004-02-10 22:41 ` Neil Brown
2004-02-10 22:41 ` Neil Brown
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=402A39B2.1010207@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.