From: Shaohua Li <shli@kernel.org>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: Shaohua Li <shli@fb.com>,
linux-raid@vger.kernel.org, Kernel-team@fb.com,
"v3.6" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] RAID1: ignore discard error
Date: Fri, 7 Oct 2016 10:42:49 -0700 [thread overview]
Message-ID: <20161007174249.GB37192@kernel.org> (raw)
In-Reply-To: <CALjAwxhSrcCaePBW0co1wSTNh0i3o0q09BKXeyeKtO_PRn+5_w@mail.gmail.com>
On Fri, Oct 07, 2016 at 11:53:07AM +0100, Sitsofe Wheeler wrote:
> On 6 October 2016 at 22:20, Shaohua Li <shli@fb.com> wrote:
> > Sitsofe,
> > could you try if this patch fixes the issue too please?
>
> As with with the previous patch the BUG_ON/crash is fixed and as
> before dmesg only says this now:
> [ 17.884175] sd 0:0:1:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [ 17.884180] sd 0:0:1:0: [sdb] tag#0 Sense Key : Illegal Request [current]
> [ 17.884185] sd 0:0:1:0: [sdb] tag#0 Add. Sense: Invalid command
> operation code
> [ 17.884190] sd 0:0:1:0: [sdb] tag#0 CDB: Write same(16) 93 08 00 00
> 00 00 00 00 40 80 00 00 08 00 00 00
> [ 17.884196] blk_update_request: critical target error, dev sdb, sector 16512
> [ 17.884205] sd 0:0:2:0: [sdc] tag#1 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [ 17.884208] sd 0:0:2:0: [sdc] tag#1 Sense Key : Illegal Request [current]
> [ 17.884211] sd 0:0:2:0: [sdc] tag#1 Add. Sense: Invalid command
> operation code
> [ 17.884215] sd 0:0:2:0: [sdc] tag#1 CDB: Write same(16) 93 08 00 00
> 00 00 00 00 40 80 00 00 08 00 00 00
> [ 17.884217] blk_update_request: critical target error, dev sdc, sector 16512
> [ 17.924716] Buffer I/O error on dev dm-0, logical block 0, async page read
>
> (sd[bc] are the devices the RAID is using)
>
> However this time around blkdiscard doesn't return an error (despite
> the discard not being done) and is quiet. It's hard to say if this is
> desirable given that the underlying devices switch to saying they
> don't support discard but perhaps that's part of a different
> discussion.
Yep, I think the spec doesn't require discard IO returns error. We probably can
make this smarter later in MD
> Tested-by: Sitsofe Wheeler <sitsofe@gmail.com>
Thanks for the testing, I'll queue the two patches.
Thanks,
Shaohua
prev parent reply other threads:[~2016-10-07 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 21:20 [PATCH 1/2] RAID1: ignore discard error Shaohua Li
2016-10-06 21:20 ` [PATCH 2/2] RAID10: " Shaohua Li
2016-10-07 10:53 ` [PATCH 1/2] RAID1: " Sitsofe Wheeler
2016-10-07 17:42 ` Shaohua Li [this message]
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=20161007174249.GB37192@kernel.org \
--to=shli@kernel.org \
--cc=Kernel-team@fb.com \
--cc=linux-raid@vger.kernel.org \
--cc=shli@fb.com \
--cc=sitsofe@gmail.com \
--cc=stable@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).