From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: dm-devel@redhat.com
Subject: Re: CONFIG_DM_MQ_DEFAULT makes my kernel unhappy..
Date: Mon, 27 Apr 2015 11:59:15 -0400 [thread overview]
Message-ID: <20150427155915.GA9976@redhat.com> (raw)
In-Reply-To: <20150426141628.GA7085@infradead.org>
On Sun, Apr 26 2015 at 10:16am -0400,
Christoph Hellwig <hch@infradead.org> wrote:
> On Sat, Apr 25, 2015 at 08:37:32AM -0700, Christoph Hellwig wrote:
> > I'll give it a spin.
> >
> > > What were you actually testing when this happened? Were you failing
> > > paths under IO load or something?
> >
> > This happened on the initial udev-direct scan of the devices.
> >
> > > Also, which upstream commit was your tree based on? Did you have any
> > > non-upstream patches applied that I should be aware of?
> >
> > Latest Linus tree as of this morning.
>
> Seems like the first warning goes away without CONFIG_DEBUG_OBJECTS.
> Note that in either way I/O over dm-mpath actually works fine.
>
> Btw, this is the script used to reproduce it, you need
> CONFIG_TARGET_CORE, CONFIG_TCM_IBLOCK and CONFIG_LOOPBACK_TARGET
> enabled. It jsut creates two different targets with a lun each,
> pointing to the same device. The target code automatically supports
> ALUA in this case.
>
> ---
> #!/bin/bash
>
> # add your own device
> #DEV=/dev/sda
>
> mount -t configfs none /sys/kernel/config/
>
> tcm_node --block iblock_0/array /dev/sda
>
> line=$(tcm_loop --createnexus=0)
> wwn=$(echo $line | awk '{print $15}')
> tcm_loop --addlun=$wwn 0 0 iblock_0/array
>
> line=$(tcm_loop --createnexus=1)
> wwn=$(echo $line | awk '{print $15}')
> tcm_loop --addlun=$wwn 1 0 iblock_0/array
>
So you're still using lio-utils? Seems "lio-utils are deprecated and
have been superseded by targetcli".. what am I missing?
What lio-utils repo should I be using to get the utils that'll work with
your script?
next prev parent reply other threads:[~2015-04-27 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 9:23 CONFIG_DM_MQ_DEFAULT makes my kernel unhappy Christoph Hellwig
2015-04-25 15:28 ` Mike Snitzer
2015-04-25 15:37 ` Christoph Hellwig
2015-04-26 14:16 ` Christoph Hellwig
2015-04-27 15:59 ` Mike Snitzer [this message]
2015-04-27 16:03 ` Christoph Hellwig
2015-04-27 19:03 ` Mike Snitzer
2015-04-29 0:59 ` [PATCH] dm: fix blk-mq request-based DM queue initialization Mike Snitzer
2015-04-29 13:00 ` Christoph Hellwig
2015-04-30 1:41 ` Mike Snitzer
2015-04-30 7:22 ` Christoph Hellwig
2015-04-30 8:23 ` Christoph Hellwig
2015-04-30 12:47 ` Mike Snitzer
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=20150427155915.GA9976@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.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