From: Mike Snitzer <snitzer@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
device-mapper development <dm-devel@redhat.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
Date: Thu, 3 Jul 2014 10:18:45 -0400 [thread overview]
Message-ID: <20140703141844.GC28104@redhat.com> (raw)
In-Reply-To: <53B56594.1060104@suse.de>
On Thu, Jul 03 2014 at 10:15am -0400,
Hannes Reinecke <hare@suse.de> wrote:
> On 07/03/2014 04:05 PM, Mike Snitzer wrote:
> >
> >Hannes, do you have a testbed for heavy cable pull testing? Are you
> >able to replicate these hangs?
> >
> Yes, I do. But sadly I've been tied up with polishing up SLES12
> (release deadline is looming nearer) and for some inexplicable
> reason management seems to find releasing a product more important
> than working on mainline issue ...
OK, so long as you didn't include these dm-mpath changes.. but if you
did then you could kill 2 birds with one stone ;)
> But I hope to find some time soonish (ie start of next week) to work
> on this; it's the very next thing on my to-do list.
OK, I really appreciate it, thanks.
next prev parent reply other threads:[~2014-07-03 14:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 13:02 v3.15 dm-mpath regression: cable pull test causes I/O hang Bart Van Assche
2014-06-27 13:33 ` Mike Snitzer
2014-06-27 14:18 ` Bart Van Assche
2014-07-02 22:02 ` Mike Snitzer
2014-07-03 5:43 ` Hannes Reinecke
2014-07-03 13:56 ` Bart Van Assche
2014-07-03 13:58 ` Hannes Reinecke
2014-07-03 14:05 ` Mike Snitzer
2014-07-03 14:15 ` Hannes Reinecke
2014-07-03 14:18 ` Mike Snitzer [this message]
2014-07-03 14:34 ` Bart Van Assche
2014-07-03 15:00 ` Mike Snitzer
2014-07-07 13:28 ` Bart Van Assche
2014-07-04 3:10 ` Junichi Nomura
2014-07-07 13:40 ` Bart Van Assche
2014-07-08 0:55 ` Junichi Nomura
2014-07-08 9:43 ` Bart Van Assche
2014-07-08 16:33 ` Mike Snitzer
2014-07-08 23:24 ` Junichi Nomura
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=20140703141844.GC28104@redhat.com \
--to=snitzer@redhat.com \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=j-nomura@ce.jp.nec.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.