From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jinpu Wang <jinpu.wang@profitbricks.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Elliott\, Robert \(Persistent Memory\)" <elliott@hpe.com>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Chaitra P B <chaitra.basappa@broadcom.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v2] block: ratelimite pr_err on IO path
Date: Fri, 13 Apr 2018 12:59:38 -0400 [thread overview]
Message-ID: <yq1bment539.fsf@oracle.com> (raw)
In-Reply-To: <CAMGffEkaTLLEs+i-EWUmo-Y8KSNBeyth63L1hXxP++PBcPPXbg@mail.gmail.com> (Jinpu Wang's message of "Fri, 13 Apr 2018 10:37:25 +0200")
Jinpu,
[CC:ed the mpt3sas maintainers]
The ratelimit patch is just an attempt to treat the symptom, not the
cause.
> Thanks for asking, we updated mpt3sas driver which enables DIX support
> (prot_mask=0x7f), all disks are SATA SSDs, no DIF support.
> After reboot, kernel reports the IO errors from all the drives behind
> HBA, seems for almost every read IO, which turns the system unusable:
> [ 13.079375] sda: ref tag error at location 0 (rcvd 143196159)
> [ 13.079989] sda: ref tag error at location 937702912 (rcvd 143196159)
> [ 13.080233] sda: ref tag error at location 937703072 (rcvd 143196159)
> [ 13.080407] sda: ref tag error at location 0 (rcvd 143196159)
> [ 13.080594] sda: ref tag error at location 8 (rcvd 143196159)
That sounds like a bug in the mpt3sas driver or firmware. I guess the
HBA could conceivably be operating a SATA device as DIX Type 0 and strip
the PI on the drive side. But that doesn't seem to be a particularly
useful mode of operation.
Jinpu: Which firmware are you running? Also, please send us the output
of:
sg_readcap -l /dev/sda
sg_inq -x /dev/sda
sg_vpd /dev/sda
Broadcom: How is DIX supposed to work for SATA drives behind an mpt3sas
controller?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-04-13 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 9:21 [PATCH v2] block: ratelimite pr_err on IO path Jack Wang
2018-04-12 21:20 ` Martin K. Petersen
2018-04-13 8:37 ` Jinpu Wang
2018-04-13 16:59 ` Martin K. Petersen [this message]
2018-04-16 8:16 ` Jinpu Wang
2018-04-16 9:06 ` Sreekanth Reddy
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=yq1bment539.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=chaitra.basappa@broadcom.com \
--cc=elliott@hpe.com \
--cc=jinpu.wang@profitbricks.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.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