From: Andrea Righi <righi.andrea@gmail.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Shaohua Li <shli@kernel.org>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: multipath: I/O hanging forever
Date: Fri, 11 Mar 2016 15:24:33 -0700 [thread overview]
Message-ID: <20160311222433.GA2617@Dell> (raw)
In-Reply-To: <20160306053103.GA31060@kmo-pixel>
On Sat, Mar 05, 2016 at 08:31:03PM -0900, Kent Overstreet wrote:
> On Fri, Mar 04, 2016 at 10:30:44AM -0700, Andrea Righi wrote:
> > On Sun, Feb 28, 2016 at 08:46:16PM -0700, Andrea Righi wrote:
> > > On Sun, Feb 28, 2016 at 06:53:33PM -0700, Andrea Righi wrote:
> > > ...
> > > > I'm using 4.5.0-rc5+, from Linus' git. I'll try to do a git bisect
> > > > later, I'm pretty sure this problem has been introduced recently (i.e.,
> > > > I've never seen this issue with 4.1.x).
> > >
> > > I confirm, just tested kernel 4.1 and this problem doesn't happen.
> >
> > Alright, I had some spare time to bisect this problem and I found that
> > the commit that introduced this issue is c66a14d.
> >
> > So, I tried to revert the commit (with some changes to fix conflicts and
> > ABI changes) and now multipath seems to work fine for me (no hung task).
>
> Is it hanging on first IO, first large IO, or just randomly?
It's always the very first O_DIRECT I/O, in general the task gets stuck
in do_blockdev_direct_IO().
Thanks,
-Andrea
next prev parent reply other threads:[~2016-03-11 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 1:53 multipath: I/O hanging forever Andrea Righi
2016-02-29 3:46 ` Andrea Righi
2016-03-04 17:30 ` Andrea Righi
2016-03-06 5:31 ` Kent Overstreet
2016-03-11 22:24 ` Andrea Righi [this message]
2016-03-12 1:47 ` Ming Lei
2016-03-12 1:47 ` Ming Lei
2016-03-13 15:29 ` Andrea Righi
2016-03-14 18:16 ` Shaohua Li
2016-03-14 7:41 ` Christoph Hellwig
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=20160311222433.GA2617@Dell \
--to=righi.andrea@gmail.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@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.