From: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: axboe@kernel.dk, satheera@in.ibm.com,
linuxppc-dev@lists.ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: System not booting since dm changes? (was Linux 4.20-rc1)
Date: Mon, 5 Nov 2018 20:05:41 +0530 [thread overview]
Message-ID: <20181105143541.GA29120@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20181105135157.GA11485@redhat.com>
On Mon, Nov 05, 2018 at 08:51:57AM -0500, Mike Snitzer wrote:
> On Mon, Nov 05 2018 at 5:25am -0500,
> Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> > Linus Torvalds <torvalds@linux-foundation.org> writes:
> > ...
> > > Mike Snitzer (1):
> > > device mapper updates
> >
> > Hi Mike,
> >
> > Replying here because I can't find the device-mapper pull or the patch
> > in question on LKML. I guess I should be subscribed to dm-devel.
> >
> > We have a box that doesn't boot any more, bisect points at one of:
> >
> > cef6f55a9fb4 Mike Snitzer dm table: require that request-based DM be layered on blk-mq devices
> > 953923c09fe8 Mike Snitzer dm: rename DM_TYPE_MQ_REQUEST_BASED to DM_TYPE_REQUEST_BASED
> > 6a23e05c2fe3 Jens Axboe dm: remove legacy request-based IO path
> >
> >
> > It's a Power8 system running Rawhide, it does have multipath, but I'm
> > told it was setup by the Fedora installer, ie. nothing fancy.
> >
> > The symptom is the system can't find its root filesystem and drops into
> > the initramfs shell. The dmesg includes a bunch of errors like below:
> >
> > [ 43.263460] localhost multipathd[1344]: sdb: fail to get serial
> > [ 43.268762] localhost multipathd[1344]: mpatha: failed in domap for addition of new path sdb
> > [ 43.268762] localhost multipathd[1344]: uevent trigger error
> > [ 43.282065] localhost kernel: device-mapper: table: table load rejected: not all devices are blk-mq request-stackable
> ...
> >
> > Any ideas what's going wrong here?
>
> "table load rejected: not all devices are blk-mq request-stackable"
> speaks to the fact that you aren't using blk-mq for scsi (aka scsi-mq).
>
> You need to use scsi_mod.use_blk_mq=Y on the kernel commandline (or set
> CONFIG_SCSI_MQ_DEFAULT in your kernel config)
Thanks Mike!, above solution worked and the system booted fine now:-)
# uname -r
4.20.0-rc1+
# cat /proc/cmdline
root=/dev/mapper/fedora_ltc--test--ci2-root ro rd.lvm.lv=fedora_ltc-test-ci2/root rd.lvm.lv=fedora_ltc-test-ci2/swap scsi_mod.use_blk_mq=Y
CONFIG_SCSI_MQ_DEFAULT kernel was not set in my kernel config, will set in future runs.
Thanks Michael!
Regards,
-Satheesh.
>
> Mike
>
next prev parent reply other threads:[~2018-11-05 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=whDiwASMgw8Q7TNA2MJhf3s=ouK4+_3ioqmobs-yagnkQ@mail.gmail.com>
2018-11-05 10:25 ` System not booting since dm changes? (was Linux 4.20-rc1) Michael Ellerman
2018-11-05 13:51 ` Mike Snitzer
2018-11-05 14:35 ` Satheesh Rajendran [this message]
2018-11-05 15:08 ` Jens Axboe
2018-11-07 0:59 ` Michael Ellerman
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=20181105143541.GA29120@MiWiFi-R3L-srv \
--to=sathnaga@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=satheera@in.ibm.com \
--cc=snitzer@redhat.com \
--cc=torvalds@linux-foundation.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).