linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Prager <linux@matthiasprager.de>
To: Baruch Even <baruch@ev-en.org>, linux-scsi <linux-scsi@vger.kernel.org>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	linux-ext4@vger.kernel.org, Chris Dunlop <chris@onthe.net.au>,
	Matthias Prager <linux@matthiasprager.de>
Subject: Re: mpt2sas + raid10 goes boom
Date: Tue, 09 Apr 2013 12:11:13 +0200	[thread overview]
Message-ID: <5163E941.1050907@matthiasprager.de> (raw)
In-Reply-To: <CAC9+anJ4pdJ7EVwDQY-QpVOVr-L3xf5STuVaZ=i9bkFz5KuO3g@mail.gmail.com>

Thanks for your insights Baruch.
The crc count did not increase any further - so this was probably just
small oddity (was zero before when the write-same issue already
happened). The real issue however does persist. I found a way to
reliably trigger the log messages. Using a program called checksum over
a photo share (which does a lot of reads and one write per file). With
that in place I switched to the 3.4.38 kernel, with which I'm unable to
trigger the problem. I will leave the system at that for now, and try to
reproduce it on my testing machine to see, whether
  c8dc9c6 md: raid1,10: Handle REQ_WRITE_SAME flag in write bios
works for me.

If c8dc9c6 does the trick, it would still be interesting to know why and
how this triggered i/o errors, the strange log message from lsi and
'Resets Between Cmd Acceptance and Completion' as one of the drives
says. Would that mean the driver/firmware from lsi is issuing or passing
on commands to the drive which it does not understand or can't process?

---
Matthias

  reply	other threads:[~2013-04-09 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 13:13 mpt2sas + raid10 goes boom Matthias Prager
2013-04-08 17:02 ` Matthias Prager
2013-04-08 20:15   ` Baruch Even
2013-04-09 10:11     ` Matthias Prager [this message]
2013-04-09 12:45       ` Matthias Prager
  -- strict thread matches above, loose matches on Subject: below --
2013-04-08  7:18 Chris Dunlop
2013-04-08  7:53 ` Chris Dunlop
2013-04-08  8:13   ` Baruch Even
2013-04-08 13:32   ` Joe Lawrence
2013-04-09  2:22     ` Chris Dunlop
2013-04-09  4:18       ` NeilBrown
2013-04-08  8:24 ` George Shuklin
2013-04-08 10:39 ` Brad Campbell

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=5163E941.1050907@matthiasprager.de \
    --to=linux@matthiasprager.de \
    --cc=baruch@ev-en.org \
    --cc=chris@onthe.net.au \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).