From: Takahiro Yasui <tyasui@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC][PATCH] Introduce the parameter to limit scsi timeout count
Date: Tue, 02 Jun 2009 16:48:06 -0400 [thread overview]
Message-ID: <4A259006.2040203@redhat.com> (raw)
In-Reply-To: <1243886558.4203.31.camel@mulgrave.int.hansenpartnership.com>
Hi James,
James Bottomley wrote:
> It doesn't really look like a good solution to the problem you're
> describing, particularly if it's just a few isolated arrays.
>
> The code you propose would certainly catch things like usb devices which
> are known for random timeouts; plus a lot of SCSI/ATA devices suffer
> isolated timeouts because of I/O load. Global code like this could end
> up offlining them.
>
> Which arrays are these, and what's the taxonomy of the failure ... if
> TUR succeeds, perhaps there's another command for the arrays we could
> send that would fail or timeout ... or perhaps there's a different way
> they should be recovered.
Thank you for the comments. I believe that this issue is not specific
to a few storages but is a general issue on a HDD storages. Therefore,
I think that adding a max timeout count on each device is one of
solutions to servers which are sensitive to delay.
But I got your point. I will try to find an implementation to not
affect other devices.
Thanks,
---
Takahiro Yasui
Hitachi Computer Products (America), Inc.
prev parent reply other threads:[~2009-06-02 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 19:15 [RFC][PATCH] Introduce the parameter to limit scsi timeout count Takahiro Yasui
2009-06-01 20:02 ` James Bottomley
2009-06-02 20:48 ` Takahiro Yasui [this message]
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=4A259006.2040203@redhat.com \
--to=tyasui@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@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.