public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Jin <joe.jin@oracle.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Joe Jin <joe.jin@oracle.com>,
	akpm@osdl.org, dgilbert@interlog.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, haobo.zhou@oracle.com
Subject: Re: [PATCH] [scsi]: Add offline state checking while dispatch a scsi cmd
Date: Mon, 12 Mar 2007 09:03:02 +0800	[thread overview]
Message-ID: <20070312010302.GA32372@joejin-pc.cn.oracle.com> (raw)
In-Reply-To: <1173626483.3420.3.camel@mulgrave.il.steeleye.com>

> 
> This is a bug actually in the megaraid.

Aha, I'll track it.

> 
> And this is a direct command submission path:  it already passed both
> online check gates in this path *after* the device was offlined, so
> adding a third won't fix this. 

Yeah, I have notice that, however, from the logs, the device have offline, 
but why still can send cmd to device? isn't the sequences of printk suspectful?

> single disk, so the I/O was definitely bound for sda?  Secondly, can you
> reproduce with a modern (2.6.20) kernel.  Your trace strongly suggests
> that the device came back online for some reason and then the megaraid
> driver died.

It's hard to update the kernel for the system is a production system, and we
cannot debug it at the box :( 

I dont know if you have notice, the logs come from diskdump, if it caused by
diskdump?

Thanks,
Joe

      reply	other threads:[~2007-03-12  1:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  9:22 [PATCH] [scsi]: Add offline state checking while dispatch a scsi cmd Joe Jin
2007-03-08 16:02 ` James Bottomley
2007-03-09  1:40   ` Joe Jin
2007-03-11  9:53     ` Andrew Morton
2007-03-12  2:52       ` Joe Jin
2007-03-12  3:15         ` Andrew Morton
2007-03-11 15:21     ` James Bottomley
2007-03-12  1:03       ` Joe Jin [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=20070312010302.GA32372@joejin-pc.cn.oracle.com \
    --to=joe.jin@oracle.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=dgilbert@interlog.com \
    --cc=haobo.zhou@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox