From: Alberto Alonso <alberto@ggsys.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>,
Mike Accetta <maccetta@laurelnetworks.com>,
Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org
Subject: Re: Software RAID when it works and when it doesn't
Date: Wed, 24 Oct 2007 15:18:58 -0500 [thread overview]
Message-ID: <1193257138.23414.88.camel@w100> (raw)
In-Reply-To: <471FA543.9090502@tmr.com>
On Wed, 2007-10-24 at 16:04 -0400, Bill Davidsen wrote:
> I think what you really want is to notice how long the drive and driver
> took to recover or fail, and take action based on that. In general "kick
> the drive" is not optimal for a few bad spots, even if the drive
> recovery sucks.
The problem is that the driver never comes back and the whole
array hangs, waiting forever. That's why a timeout within the
md code is needed to recover from these type of drivers.
Alberto
next prev parent reply other threads:[~2007-10-24 20:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 18:40 Software RAID when it works and when it doesn't Alberto Alonso
2007-10-13 22:46 ` Eyal Lebedinsky
2007-10-13 22:50 ` Neil Brown
2007-10-14 5:57 ` Alberto Alonso
2007-10-16 21:57 ` Mike Accetta
2007-10-16 22:29 ` Richard Scobie
2007-10-17 21:53 ` Support
2007-10-18 15:26 ` Goswin von Brederlow
2007-10-19 7:07 ` Alberto Alonso
2007-10-19 15:02 ` Justin Piszcz
2007-10-20 13:45 ` Michael Tokarev
2007-10-20 13:55 ` Justin Piszcz
2007-10-26 16:11 ` Goswin von Brederlow
2007-10-26 16:11 ` Justin Piszcz
2007-10-23 22:45 ` Bill Davidsen
2007-10-24 5:50 ` Alberto Alonso
2007-10-24 20:04 ` Bill Davidsen
2007-10-24 20:18 ` Alberto Alonso [this message]
2007-10-26 16:12 ` Goswin von Brederlow
2007-10-26 17:09 ` Alberto Alonso
2007-10-27 15:26 ` Bill Davidsen
2007-11-02 8:47 ` Alberto Alonso
[not found] ` <471241F8.50205@harddata.com>
2007-10-14 18:22 ` Alberto Alonso
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=1193257138.23414.88.camel@w100 \
--to=alberto@ggsys.net \
--cc=brederlo@informatik.uni-tuebingen.de \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=maccetta@laurelnetworks.com \
--cc=neilb@suse.de \
/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).