From: scameron@beardog.cce.hp.com
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jon Mason <mason@myri.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
stephenmcameron@gmail.com, thenzl@redhat.com,
akpm@linux-foundation.org, mikem@beardog.cce.hp.com,
linux-pci@vger.kernel.org, Roland Dreier <roland@purestorage.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [BUG] scsi: hpsa: how to destroy your files
Date: Fri, 2 Sep 2011 10:03:21 -0500 [thread overview]
Message-ID: <20110902150321.GU9189@beardog.cce.hp.com> (raw)
In-Reply-To: <1314958133.2573.13.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
On Fri, Sep 02, 2011 at 12:08:53PM +0200, Eric Dumazet wrote:
> Le vendredi 02 septembre 2011 à 11:39 +0200, Eric Dumazet a écrit :
> > Le jeudi 01 septembre 2011 à 16:50 -0500, Jon Mason a écrit :
> >
> > > I believe modifying the MRRS values is what is causing the issues.
> > > Can you try the attached patch and verify that it also resolves the
> > > issue?
> >
> > I tested this patch and can confirm this solves the corruption problem.
> >
> > But my disk is _much_ slower than before
> >
> > # hdparm -t /dev/sda1
> >
> > Before :
> >
> > Timing buffered disk reads: 254 MB in 3.02 seconds = 84.16 MB/sec
> >
> > After :
> >
> > Timing buffered disk reads: 120 MB in 3.04 seconds = 39.42 MB/sec
>
> Hmm, this speed regression is probably old : the 84MB/s was with the
> standard debian 6.0.2 kernel (2.6.32-5-amd64)
>
This regression might be due to these two patches:
d0be5ec8693944c2e2fc0de70fda9dbc1b93bd7d
[SCSI] hpsa: do readl after writel in main i/o path to ensure commands don't get lost.
Apparently we've been doin it rong for a decade, but only lately do we
run into problems.
and
fec62c368b9c8b05d5124ca6c3b8336b537f26f3
[SCSI] hpsa: do not attempt to read from a write-only register
Most smartarrays tolerate it, but a few new ones don't.
Without this change some newer Smart Arrays will lock up
and i/o will grind to a halt.
with the second patch being a correction to the first.
It seems like the readl after the writel should not be needed,
and wasn't needed for a very long time, but there is some very
hard to trigger and not yet well understood problem in which very
occasionally a command would get lost and the driver thinks a
command is out, but controller firmware thinks all commands are
completed -- a circumstance which tends to make things grind to
a halt.
Those two patches avoid that problem.
-- steve
next prev parent reply other threads:[~2011-09-02 15:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 18:16 [PATCH] hpsa: do not attempt to read from a write-only register Stephen M. Cameron
2011-07-21 18:17 ` Stephen Cameron
2011-07-22 22:39 ` Andrew Morton
2011-09-01 15:24 ` [BUG] scsi: hpsa: how to destroy your files Eric Dumazet
2011-09-01 16:07 ` scameron
2011-09-01 16:18 ` Eric Dumazet
2011-09-01 17:40 ` Eric Dumazet
2011-09-01 17:58 ` Roland Dreier
2011-09-01 18:50 ` James Bottomley
2011-09-01 18:58 ` Jesse Barnes
2011-09-01 19:59 ` Jesse Barnes
[not found] ` <20110901200349.GO9189@beardog.cce.hp.com>
2011-09-01 20:09 ` Jesse Barnes
2011-09-01 20:44 ` scameron
2011-09-01 21:50 ` Jon Mason
2011-09-01 22:01 ` Eric Dumazet
2011-09-01 22:16 ` scameron
2011-09-02 5:32 ` Eric Dumazet
2011-09-02 9:39 ` Eric Dumazet
2011-09-02 10:08 ` Eric Dumazet
2011-09-02 15:03 ` scameron [this message]
2011-09-01 19:36 ` Eric Dumazet
2011-09-01 18:01 ` scameron
2011-09-01 19:03 ` scameron
2011-09-02 23:13 ` Andrew Morton
2011-09-02 5:18 ` Mike Galbraith
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=20110902150321.GU9189@beardog.cce.hp.com \
--to=scameron@beardog.cce.hp.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mason@myri.com \
--cc=mikem@beardog.cce.hp.com \
--cc=roland@purestorage.com \
--cc=stephenmcameron@gmail.com \
--cc=thenzl@redhat.com \
/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
all inboxes | Powered by JetHome®