From: Byron Stanoszek <gandalf@winds.org>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Mark Haverkamp <markh@osdl.org>, Alan Cox <alan@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: RE: PATCH: Further aacraid work
Date: Tue, 29 Jun 2004 15:03:29 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0406291454370.26639@winds.org> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189FF1D6BA@otce2k03.adaptec.com>
On Tue, 29 Jun 2004, Salyzyn, Mark wrote:
> I believe this nails the problem too.
>
> However, there is a corner case condition lurking on this (See my
> currently unanswered email "error recovery and command completion" on
> linux-scsi) where I try to deal with completing a command while error
> recovery is triggered. Scsi_done will return doing *nothing* effectively
> loosing the command completion.
>
> MarkH, I had talked to you about he addition of the scsi_add_timer
> before calling scsi_done to address this condition. I do not believe
> this to be the (Reliable and/or performance oriented) solution.
>
> Sincerely -- Mark Salyzyn
I've tested out both patches sent to me.
Test 1: aacraid-1.1.5-2245.tgz
Works flawlessly and speedily! The rsync completes, and doing a sync() (as
called during a normal lilo update) takes roughly 1 second as opposed to 20
with the original aacraid patch from Alan Cox. Also, no SCSI hang message ever
appears.
Test 2: Mark Haverkamp's linit.c patch
The "SCSI hang" console message appears just as before during the 'rsync',
however (unlike before) the device is still usable for roughly 30 seconds after
the problem. During these 30 seconds, the 'rsync' process is hung, but I can
still do a 'df', 'ls', and so on. After 30 seconds, the entire /dev/sda locks
up and I have no choice but to reboot the system.
-Byron
next prev parent reply other threads:[~2004-06-29 19:03 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 18:53 PATCH: Further aacraid work Salyzyn, Mark
2004-06-29 19:03 ` Byron Stanoszek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-29 20:55 Salyzyn, Mark
2004-06-29 23:22 ` Byron Stanoszek
2004-06-30 19:52 ` Byron Stanoszek
2004-06-30 19:59 ` Dario
2004-06-29 19:27 Salyzyn, Mark
2004-06-29 20:20 ` Byron Stanoszek
2004-06-29 20:42 ` Alan Cox
2004-06-28 13:17 Salyzyn, Mark
2004-06-18 20:53 Salyzyn, Mark
2004-06-18 20:53 ` Salyzyn, Mark
[not found] <286GI-5y3-11@gated-at.bofh.it>
[not found] ` <286Qp-5EU-19@gated-at.bofh.it>
2004-06-17 19:10 ` Andi Kleen
2004-06-17 20:54 ` Alan Cox
2004-06-17 21:13 ` James Bottomley
2004-06-17 21:25 ` Andi Kleen
2004-06-18 15:19 ` Benjamin Herrenschmidt
2004-06-18 5:57 ` Jeff Garzik
2004-06-18 14:07 ` James Bottomley
2004-06-18 15:17 ` Benjamin Herrenschmidt
2004-06-17 17:54 Salyzyn, Mark
2004-06-17 20:38 ` Alan Cox
2004-06-17 20:48 ` William Lee Irwin III
2004-06-17 20:56 ` James Bottomley
2004-06-18 15:05 ` William Lee Irwin III
2004-06-18 20:32 ` William Lee Irwin III
2004-06-27 17:33 ` James Bottomley
2004-06-17 14:39 Salyzyn, Mark
2004-06-17 14:39 ` Salyzyn, Mark
2004-06-17 14:55 ` James Bottomley
2004-06-17 14:58 ` Alan Cox
2004-06-17 15:15 ` Arjan van de Ven
2004-06-17 19:16 ` James Bottomley
2004-06-17 16:32 ` Clay Haapala
2004-06-17 16:37 ` James Bottomley
2004-06-17 16:46 ` Alan Cox
2004-06-17 15:11 ` Anton Blanchard
2004-06-17 12:53 Salyzyn, Mark
2004-06-17 12:53 ` Salyzyn, Mark
2004-06-17 13:07 ` Matthew Wilcox
2004-06-17 13:19 ` Christoph Hellwig
2004-06-17 13:55 ` James Bottomley
2004-06-17 13:32 ` Christoph Hellwig
2004-06-17 14:02 ` Alan Cox
2004-06-16 21:04 Alan Cox
2004-06-16 21:33 ` Christoph Hellwig
2004-06-16 21:40 ` Alan Cox
2004-06-16 21:42 ` Christoph Hellwig
2004-06-16 21:48 ` Alan Cox
2004-06-16 21:58 ` Christoph Hellwig
2004-06-16 22:06 ` Alan Cox
2004-06-29 17:48 ` Byron Stanoszek
2004-06-29 18:27 ` Mark Haverkamp
2004-06-29 18:37 ` Alan Cox
2004-06-30 2:02 ` bm
2004-06-30 16:07 ` Alan Cox
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=Pine.LNX.4.60.0406291454370.26639@winds.org \
--to=gandalf@winds.org \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=markh@osdl.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.