From: Brian King <brking@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
Ryan Anderson <ryan@autoweb.net>,
linux-scsi@vger.kernel.org
Subject: Re: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraidPERC 3/Di Container goes offline
Date: Wed, 24 Nov 2004 08:58:59 -0600 [thread overview]
Message-ID: <41A4A1B3.5070106@us.ibm.com> (raw)
In-Reply-To: <20041124130904.GA12830@infradead.org>
Christoph Hellwig wrote:
> On Wed, Nov 24, 2004 at 07:59:04AM -0500, Salyzyn, Mark wrote:
>
>>I dropped Andrew Morton from the direct mail recipients.
>>
>>Thanks, made the change in my branch of the code. This adjustment will
>>probably never be submitted to MarkH since I use it only for debugging
>>purposes. However, would it be nice if the global scsi timeout could be
>>`user' adjustable?
>>
>>Not that I advocate it as readily accessible, since any storage device
>>that takes longer than ten seconds is in `trouble', and any timeout
>>longer than two minutes will no doubt cause servers to go offline on the
>>internet. Its purpose is only for troubleshooting.
>
>
> Yes, it would probably be nice to have a writeable timeout attribute for
> the scsi device. Care to submit a patch?
This already exists today.
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2004-11-24 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 12:59 Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraidPERC 3/Di Container goes offline Salyzyn, Mark
2004-11-24 13:09 ` Christoph Hellwig
2004-11-24 14:58 ` Brian King [this message]
2004-11-24 20:29 ` Mike Christie
2004-11-24 20:28 ` Brian King
2004-11-24 20:31 ` Mike Christie
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 22:07 Salyzyn, Mark
2004-11-23 22:15 ` Ryan Anderson
2004-11-23 22:35 ` Christoph Hellwig
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=41A4A1B3.5070106@us.ibm.com \
--to=brking@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=ryan@autoweb.net \
/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