From: Jinpu Wang <jinpu.wang@profitbricks.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
Subject: Re: [PATCH v2] block: ratelimite pr_err on IO path
Date: Fri, 13 Apr 2018 10:37:25 +0200 [thread overview]
Message-ID: <CAMGffEkaTLLEs+i-EWUmo-Y8KSNBeyth63L1hXxP++PBcPPXbg@mail.gmail.com> (raw)
In-Reply-To: <yq1y3hsunnt.fsf@oracle.com>
On Thu, Apr 12, 2018 at 11:20 PM, Martin K. Petersen
<martin.petersen@oracle.com> wrote:
>
> Jack,
>
>> + pr_err_ratelimited("%s: ref tag error at location %llu (rcvd %u)\n",
>
> I'm a bit concerned about dropping records of potential data loss.
>
> Also, what are you doing that compels all these to be logged? This
> should be a very rare occurrence.
>
> --
> Martin K. Petersen Oracle Linux Engineering
Hi Martin,
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)
[ 13.080996] sda: ref tag error at location 0 (rcvd 143196159)
[ 13.089878] sdb: ref tag error at location 0 (rcvd 143196159)
[ 13.090275] sdb: ref tag error at location 937702912 (rcvd 277413887)
[ 13.090448] sdb: ref tag error at location 937703072 (rcvd 143196159)
[ 13.090655] sdb: ref tag error at location 0 (rcvd 143196159)
[ 13.090823] sdb: ref tag error at location 8 (rcvd 277413887)
[ 13.091218] sdb: ref tag error at location 0 (rcvd 143196159)
[ 13.095412] sdc: ref tag error at location 0 (rcvd 143196159)
[ 13.095859] sdc: ref tag error at location 937702912 (rcvd 143196159)
[ 13.096058] sdc: ref tag error at location 937703072 (rcvd 143196159)
[ 13.096228] sdc: ref tag error at location 0 (rcvd 143196159)
[ 13.096445] sdc: ref tag error at location 8 (rcvd 143196159)
[ 13.096833] sdc: ref tag error at location 0 (rcvd 277413887)
[ 13.097187] sds: ref tag error at location 0 (rcvd 277413887)
[ 13.097707] sds: ref tag error at location 937702912 (rcvd 143196159)
[ 13.097855] sds: ref tag error at location 937703072 (rcvd 277413887)
Kernel version 4.15 and 4.14.28, I scan the commits in upstream,
haven't found any relevant.
in 4.4.112, there's no such errors.
Diable DIX support (prot_mask=0x7) in mpt3sas fixes the problem.
Regards,
--
Jack Wang
Linux Kernel Developer ProfitBricks GmbH
next prev parent reply other threads:[~2018-04-13 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 9:21 Jack Wang
2018-04-12 21:20 ` Martin K. Petersen
2018-04-13 8:37 ` Jinpu Wang [this message]
2018-04-13 16:59 ` Martin K. Petersen
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=CAMGffEkaTLLEs+i-EWUmo-Y8KSNBeyth63L1hXxP++PBcPPXbg@mail.gmail.com \
--to=jinpu.wang@profitbricks.com \
--cc=axboe@kernel.dk \
--cc=elliott@hpe.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.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®