linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Prager <linux@matthiasprager.de>
To: Tejun Heo <tj@kernel.org>
Cc: Robert Trace <maillist@farcaster.org>,
	linux-scsi@vger.kernel.org, Jens Axboe <jaxboe@fusionio.com>
Subject: Re: 'Device not ready' issue on mpt2sas since 3.1.10
Date: Tue, 17 Jul 2012 21:39:41 +0200	[thread overview]
Message-ID: <5005BF7D.2050703@matthiasprager.de> (raw)
In-Reply-To: <20120717180932.GB2878@google.com>

Hello Tejun,

Am 17.07.2012 20:09, schrieb Tejun Heo:
> Hello,
> 
> On Wed, Jul 11, 2012 at 03:48:00PM +0200, Matthias Prager wrote:
>> I'm trying to understand why this commit leads to the issue of i/o
>> failing on spun down drives, in hopes of being able to fix it. Meanwhile
>> maybe Tejun Heo (author of the commit) or Jens Axboe (the committer) are
>> able to shed some light on this (I've included them in the CC list).
> 
> Nothing rings a bell for me.  How does it fail?  The only thing it
> change is when and which media check commands are issued.

I will try to describe the issue as best as I can (please feel free to
point me to more helpful debugging steps or guides):
Whenever I put a drive to sleep (either via 'hdparm -y ...' or by
letting it run into standby timeout) and issue i/o's afterwards (like
with the help of 'fdisk -l') I get back i/o errors (along the lines of
'end_request: I/O error, ...' - see previous posts in this thread) and
the drive remains in standby (instead of waking up).

Robert (who also saw these errors) bisected the issue down to your
patch. And without it kernels 3.1.10 + 3.4.4 run smoothly for him and me.

I could not however reproduce the issue on any other device than a LSI
SAS controller (using SATA disks) - on a regular ICH10 using AHCI and a
SATA drive I don't see these i/o errors. But since I'm experiencing
these issues on two different systems (both with lsi controllers while
running vmware-guests on them) and Robert sees them on his
(non-virtualized) system with the same lsi controller (9211-8i), I'm
inclined to make the following assumptions:
Either it is an issue which is limited to this controller and possibly
sata disks hanging off it or it is a more general issue with sas
controllers and sata disks (again it could well affect sas disks too).
Lacking other controllers or sas disks I can't be sure.

Thank you for taking the time to look into this - it's much appreciated
Matthias

  reply	other threads:[~2012-07-17 19:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 11:19 'Device not ready' issue on mpt2sas since 3.1.10 Matthias Prager
2012-07-09 14:40 ` Matthias Prager
2012-07-09 19:37   ` Robert Trace
2012-07-09 20:45     ` Darrick J. Wong
2012-07-09 22:24       ` Robert Trace
2012-07-10  0:21         ` Matthias Prager
2012-07-10  1:56           ` Robert Trace
2012-07-10 16:54         ` Darrick J. Wong
2012-07-10  0:12     ` Matthias Prager
2012-07-10  1:51       ` Robert Trace
2012-07-10 23:27         ` Robert Trace
2012-07-11 12:19           ` Matthias Prager
2012-07-11 13:48             ` Matthias Prager
2012-07-17 18:09               ` Tejun Heo
2012-07-17 19:39                 ` Matthias Prager [this message]
2012-07-17 20:01                   ` Tejun Heo
2012-07-21 12:15                     ` Matthias Prager
2012-07-22 17:31                       ` Tejun Heo
2012-07-22 23:14                         ` Matthias Prager
2012-07-23 15:26                           ` Tejun Heo
2012-07-24 22:04                             ` Matthias Prager
2012-07-25 10:26                               ` Reddy, Sreekanth
2012-07-25 14:19                         ` James Bottomley
2012-07-25 17:17                           ` Tejun Heo
2012-07-25 19:55                             ` James Bottomley
2012-07-25 23:56                               ` Matthias Prager
2012-07-26 19:16                                 ` Robert Trace
2012-08-16 18:26                               ` Robert Trace
2012-08-16 20:24                                 ` Matthias Prager
2012-08-16 20:33                                   ` Robert Trace
2012-07-25 22:35                         ` tomm
2012-07-26 19:20                           ` Robert Trace
2012-07-09 22:08   ` NeilBrown
2012-07-10  0:03     ` Matthias Prager
  -- strict thread matches above, loose matches on Subject: below --
2015-11-27 10:28 Felix Matouschek

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=5005BF7D.2050703@matthiasprager.de \
    --to=linux@matthiasprager.de \
    --cc=jaxboe@fusionio.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=maillist@farcaster.org \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).