From: Tejun Heo <tj@kernel.org>
To: Matthias Prager <linux@matthiasprager.de>
Cc: Robert Trace <maillist@farcaster.org>,
linux-scsi@vger.kernel.org, Jens Axboe <jaxboe@fusionio.com>,
Eric Moore <Eric.Moore@lsi.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Alan <alan@lxorguk.ukuu.org.uk>,
"Darrick J. Wong" <djwong@us.ibm.com>,
Matthias Prager <linux@matthiaspragers.de>
Subject: Re: 'Device not ready' issue on mpt2sas since 3.1.10
Date: Mon, 23 Jul 2012 08:26:19 -0700 [thread overview]
Message-ID: <20120723152619.GD6823@google.com> (raw)
In-Reply-To: <500C8938.2080607@matthiasprager.de>
Hello,
On Mon, Jul 23, 2012 at 01:14:00AM +0200, Matthias Prager wrote:
> as it turns out my workaround (setting allow_restart=1) isn't all that
> useful after all. There are no more i/o errors because the drive just
> never goes to standby mode anymore (at least 'hdparm -y /dev/sda' does
> not seem to have any effect anymore). I don't really understand why - do
> sas drives ever get to standby mode? (they have allow_restart=1 set by
> default) And is this desired or expected behavior for sata disk on sas
> controllers?
>
> For the moment the only way for me to have my sata drives sleeping
> without i/o errors is to revert your original commit
> (85ef06d1d252f6a2e73b678591ab71caad4667bb - tested with kernels 3.1.10,
> 3.4.4, 3.4.5, 3.4.6 and 3.5.0)
Hmmm... I think we definitely need help from mpt people. Ping, guys.
> P.S. I hope I'm not getting on everybody's nerves here (especially yours
> Tejun)
Not at all. :)
Thanks.
--
tejun
next prev parent reply other threads:[~2012-07-23 15:26 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
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 [this message]
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=20120723152619.GD6823@google.com \
--to=tj@kernel.org \
--cc=Eric.Moore@lsi.com \
--cc=JBottomley@parallels.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=djwong@us.ibm.com \
--cc=jaxboe@fusionio.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@matthiasprager.de \
--cc=linux@matthiaspragers.de \
--cc=maillist@farcaster.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).