From: Pierre Beck <mail@pierre-beck.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
Date: Tue, 02 Oct 2012 01:54:47 +0200 [thread overview]
Message-ID: <506A2D25.2040904@pierre-beck.de> (raw)
In-Reply-To: <2A7CFE69-08F3-4C53-928C-A94907027CAC@colorremedies.com>
Yes. When in degraded mode, timeout should be raised to five minutes or
so. When in clean mode, timeout should be a tunable in milliseconds.
Commercial RAIDs offer timeouts in ranges like 200ms - 2s. Plus a disk
which was kicked that way should be scanned for and re-added if
possible. With write-intent bitmaps, that would make RAIDs with aging
disks or cables much more solid.
Also, non-degraded mode: Skip loop resets. Skip all resets actually, if
possible. Just kick the disk. Degraded mode: Perform loop resets as it
is now. A hung-up controller would then cause an array to degrade, but
won't hang indefinitely. Granted, always doing loop resets keeps the
array non-degraded, but a crashed controller is rare whilst failing
disks are common.
linux-scsi and linux-raid should talk about this one day to make it
happen. Requires a bit of interfacing between the layers.
On 02.10.2012 00:53, Chris Murphy wrote:
> On Oct 1, 2012, at 3:33 PM, Pierre Beck wrote:
>> It's particularly annoying when in RAID and the disk could've simply been kicked within few seconds. Something that needs improvement IMHO.
> Except that while this helps with faster recovery, you're now degraded. You wouldn't want this "fast recovery" behavior if you're at your critical number of disks remaining or you lose the array upon a few seconds worth of subsequent problems. So we kinda need context specific behavior.
>
>
> Chris Murphy--
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-10-01 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 18:52 Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller? Nix
2012-09-19 20:19 ` Chris Murphy
2012-09-23 15:41 ` Nix
2012-10-01 21:33 ` Pierre Beck
2012-10-01 22:46 ` Chris Murphy
2012-10-01 23:54 ` Pierre Beck [this message]
2012-10-02 0:10 ` Nix
2012-09-19 22:30 ` Stan Hoeppner
2012-09-20 6:51 ` Nix
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=506A2D25.2040904@pierre-beck.de \
--to=mail@pierre-beck.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.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).