All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks"
Date: Tue, 13 Mar 2018 13:07:22 -0400	[thread overview]
Message-ID: <20180313170721.GA3262@redhat.com> (raw)
In-Reply-To: <20180313170210.GD2785@redhat.com>

On Tue, Mar 13 2018 at  1:02pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:

> On Tue, Mar 13 2018 at 12:43pm -0400,
> Bart Van Assche <Bart.VanAssche@wdc.com> wrote:
> 
> > On Mon, 2018-03-12 at 21:23 -0400, Mike Snitzer wrote:
> > > Anyway, I'm hopeful I fixed the issue you reported.  Please feel free to
> > > test the 2 topmost commits I've staged in linux-next, via dm-4.16:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-4.16
> > 
> > So far I haven't seen the crash I reported yesterday in my tests with dm-4.16
> > of this morning. But I see hanging dm requests. I did not see any such issue
> > yesterday with the revert I posted applied on top of dm-4.16. What I see today
> > in the logs is the following:
> > 
> > INFO: task kworker/3:150:1681 blocked for more than 120 seconds
> > 
> > and in debugfs:
> > # (cd /sys/kernel/debug/block/ && grep -r op= .)
> > ./dm-2/requeue_list:00000000df366fff {.op=READ, .cmd_flags=, .rq_flags=SORTED|STARTED|SOFTBARRIER|ELVPRIV|IO_STAT, .state=idle, .tag=-1, .internal_tag=45}
> > ./dm-0/requeue_list:000000008302ea45 {.op=READ, .cmd_flags=, .rq_flags=SORTED|STARTED|SOFTBARRIER|ELVPRIV|IO_STAT, .state=idle, .tag=-1, .internal_tag=211}
> > ./dm-1/requeue_list:000000007ea8ad0e {.op=READ, .cmd_flags=, .rq_flags=SOFTBARRIER|IO_STAT, .state=idle, .tag=428, .internal_tag=-1}
> > ./dm-1/requeue_list:00000000e93ecaa8 {.op=READ, .cmd_flags=, .rq_flags=SOFTBARRIER|IO_STAT, .state=idle, .tag=429, .internal_tag=-1}
> 
> Strange.. but I'll review closer.  Clearly requests aren't getting
> pulled off the request_list

Just a thought: Maybe dm-4.16 (rc4 based) is missing a blk-mq fix?

Might be worth cherry-picking the 2 topmost commits from dm-4.16 into
the linus-based (rc5) tree you reported the original issue against?

(looking at jens' rc5 block pull request, it seems unlikely but...)

  reply	other threads:[~2018-03-13 17:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 20:28 [PATCH] Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks" Bart Van Assche
2018-03-12 21:23 ` Mike Snitzer
2018-03-12 21:32   ` Bart Van Assche
2018-03-13  1:23     ` Mike Snitzer
2018-03-13 16:43       ` Bart Van Assche
2018-03-13 17:02         ` Mike Snitzer
2018-03-13 17:07           ` Mike Snitzer [this message]
2018-03-13 17:10             ` Bart Van Assche
2018-03-13 21:41               ` Mike Snitzer
2018-03-14 16:34                 ` Bart Van Assche
2018-03-13 15:25     ` Mike Snitzer
2018-03-13 16:31       ` Mike Snitzer
2018-03-13 16:46         ` Bart Van Assche
2018-03-13 16:58           ` Mike Snitzer
2018-03-30 17:04         ` Bart Van Assche
2018-03-13 16:38       ` Bart Van Assche

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=20180313170721.GA3262@redhat.com \
    --to=snitzer@redhat.com \
    --cc=Bart.VanAssche@wdc.com \
    --cc=dm-devel@redhat.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 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.