From: Neil Brown <neilb@suse.de>
To: Berkey B Walker <berk@panix.com>
Cc: linux raid <linux-raid@vger.kernel.org>
Subject: Re: Possibility for a parallel relaxed RAID?
Date: Fri, 19 Mar 2010 08:54:14 +1100 [thread overview]
Message-ID: <20100319085414.6cdddd29@notabene.brown> (raw)
In-Reply-To: <4BA27898.4010907@panix.com>
On Thu, 18 Mar 2010 15:01:44 -0400
Berkey B Walker <berk@panix.com> wrote:
> There maybe many folks out there who want to use RAID on their personal,
> non-production systems. Assuming access and thru-put values are not
> critical a problem might be "You can't use Desktop drives for RAID".
> Which, I think, most of us know is not really true, but - - If the
> timing issues were to be relaxed, allowing the drive to fix itself,
> before being kicked by the md process, might not the average Joe be
> better served? There is a big difference between going a mile and
> buying a commodity drive, and being "up" in an hour vs. finding a
> working system, going online, paying price+, and getting/paying fast
> shipping. Which might resolve the issue in days instead of hours.
>
> Any possibility of a parallel, less critical to drive response, release
> of md? Or a patch to allow same?
This is not a function of 'md'. md has no timeouts for drives responding.
It just submits a request and waits for a success/fail reply.
It may be a function of the lower level SATA/SCSI/FC/whatever driver. You
would do better to ask the developers of those drivers, maybe start with the
maintainer of libata.
NeilBrown
next prev parent reply other threads:[~2010-03-18 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 19:01 Possibility for a parallel relaxed RAID? Berkey B Walker
2010-03-18 21:54 ` Neil Brown [this message]
2010-03-18 23:00 ` Randy Terbush
2010-03-19 1:54 ` 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=20100319085414.6cdddd29@notabene.brown \
--to=neilb@suse.de \
--cc=berk@panix.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 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.