All of lore.kernel.org
 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>,
	linux-raid <linux-raid@vger.kernel.org>
Cc: Matthias Prager <linux@matthiasprager.de>,
	linux-ext4@vger.kernel.org, Chris Dunlop <chris@onthe.net.au>
Subject: Re: mpt2sas + raid10 goes boom
Date: Tue, 09 Apr 2013 14:45:48 +0200	[thread overview]
Message-ID: <51640D7C.9060106@matthiasprager.de> (raw)
In-Reply-To: <5163E941.1050907@matthiasprager.de>

Hello everyone,

an update: I was able to reproduce the problem on my testing
machine (at least sort of) and confirmed that
  c8dc9c6 md: raid1,10: Handle REQ_WRITE_SAME flag in write bios
fixes things.
Also applied c8dc9c6 to the main system's 3.8.6 kernel. Working without
any issues.

One interesting detail: on the testing system's 9240-8i lsi controller
(megaraid_sas instead of mpt2sas driver) the log messages where
different and seemingly not coming from controller errors:

Apr  9 12:59:17 kernel: bio too big device sdb (4096 > 256)
Apr  9 12:59:17 kernel: md12: WRITE SAME failed. Manually zeroing.

Whereas the lsi 9211-8i gave these messages:

[ 2772.726292] mpt2sas0: log_info(0x31120320): originator(PL), code(0x12), sub_code(0x0320)
[ 2772.726296] mpt2sas0: log_info(0x31120320): originator(PL), code(0x12), sub_code(0x0320)
[ 2772.940873] mpt2sas0: log_info(0x31120320): originator(PL), code(0x12), sub_code(0x0320)
[ 2773.205568] mpt2sas0: log_info(0x31120320): originator(PL), code(0x12), sub_code(0x0320)
[ 2773.953718] mpt2sas0: log_info(0x31120320): originator(PL), code(0x12), sub_code(0x0320)
[ 2774.203121] mpt2sas0: log_info(0x31120320): originator(PL), code(0x12), sub_code(0x0320)
[ 2774.452462] mpt2sas0: log_info(0x31120320): originator(PL), code(0x12), sub_code(0x0320)
[ 2774.452476] sd 0:0:4:0: [sde] Unhandled error code
[ 2774.452479] sd 0:0:4:0: [sde]  
[ 2774.452480] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK
[ 2774.452482] sd 0:0:4:0: [sde] CDB: 
[ 2774.452483] Write(10): 2a 00 a9 84 24 08 00 00 08 00
[ 2774.452491] end_request: I/O error, dev sde, sector 2844009480
[ 2774.452636] md3: WRITE SAME failed. Manually zeroing.

The former one looks a lot more friendly to me.

@lsi guys: this reveals a bug in the mpt2sas driver and/or
           the 9211&co series firmware, correct?

Thanks everyone for your help so far,
Matthias

  reply	other threads:[~2013-04-09 12:45 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
2013-04-09 12:45       ` Matthias Prager [this message]
  -- 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=51640D7C.9060106@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.