linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Spelic <spelic@shiftmail.org>
To: Spelic <spelic@shiftmail.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	open-iscsi@googlegroups.com, scst-devel@lists.sourceforge.net
Subject: Re: on-off periodic hangs in scsi commands
Date: Thu, 06 Jan 2011 22:06:51 +0100	[thread overview]
Message-ID: <4D262EEB.9070303@shiftmail.org> (raw)
In-Reply-To: <4D24BEC4.7040906@shiftmail.org>

On 01/05/2011 07:56 PM, Spelic wrote:
> Hello
> I am on kernel 2.6.36.2  (but I think I saw this problem also long 
> time ago on 2.6.31)
> I am having problems of greatly reduced throughput to scsi devices
>
> ...with 3ware...
> ...and now with iscsi...

Please disregard the whole iSCSI thing, iSCSI works perfectly!
I forgot I had a firewall test running simultaneously, I'm just 
stupid... let's not even talk about it :-(



The 3ware thing is real though, but I guess it's some kind of 3ware bug. 
Difficult to say for sure until I can get my hands on another controller.
Strange thing only one MD array has that problem even though there are 
other similar MD raid5 arrays on the same controller and other identical 
controllers.
It can't be a damaged disk because writes get stuck cyclically on all 6 
drives of that array.
Even cables can't be: they are cables for 4 drives each, and 2 drives 
are together with other 2 drives on another MD array which doesn't show 
the problem.

Is there any way to tell Linux to poll a PCI device even if it hasn't 
received an interrupt from it?
If I could poll the controller every, say, 0.2 sec I could test if the 
problem goes away.

Thank you

      parent reply	other threads:[~2011-01-06 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 18:56 on-off periodic hangs in scsi commands Spelic
     [not found] ` <4D24BEC4.7040906-9AbUPqfR1/2XDw4h08c5KA@public.gmane.org>
2011-01-06 19:25   ` Vladislav Bolkhovitin
2011-01-06 21:06 ` Spelic [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=4D262EEB.9070303@shiftmail.org \
    --to=spelic@shiftmail.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=open-iscsi@googlegroups.com \
    --cc=scst-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).