Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1670966 - set ACT_CREATE (map does not exist)
Summary: set ACT_CREATE (map does not exist)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 28
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: oVirt_on_Fedora
TreeView+ depends on / blocked
 
Reported: 2019-01-30 13:02 UTC by Kapetanakis Giannis
Modified: 2019-05-28 23:39 UTC (History)
26 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:39:40 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
multipath.conf (1.38 KB, text/plain)
2019-01-30 13:02 UTC, Kapetanakis Giannis 		no flags Details
multipath -v3 (28.90 KB, text/plain)
2019-01-30 13:03 UTC, Kapetanakis Giannis 		no flags Details
View All

Description Kapetanakis Giannis 2019-01-30 13:02:33 UTC 
Created attachment 1525029 [details]
multipath.conf

Hi,

After updating today to 4.20.4-100.fc28.x86_64 multipath has stopped working.
This an iSCSI connection to a Dell MD3200i with 4 paths.
I use full disk and no partition/LVM.
Last good kernel was 4.19.13-200.fc28.x86_64

In multipath -v3 
the obvious errors are:
Jan 30 14:50:45 | md3200: assembled map [3 pg_init_retries 50 queue_if_no_path 1 rdac 1 1 service-time 0 4 1 8:112 2 8:144 2 8:128 2 8:160 2
]
Jan 30 14:50:45 | md3200: set ACT_CREATE (map does not exist)
Jan 30 14:50:45 | md3200: failed to load map, error 22
Jan 30 14:50:45 | md3200: domap (0) failure for create/reload map
Jan 30 14:50:45 | md3200: ignoring map

see all log in attachment

# lsscsi 
[10:0:0:0]   disk    DELL     MD32xxi          0820  /dev/sdh 
[10:0:0:31]  disk    DELL     Universal Xport  0820  -        
[11:0:0:0]   disk    DELL     MD32xxi          0820  /dev/sdj 
[11:0:0:31]  disk    DELL     Universal Xport  0820  -        
[12:0:0:0]   disk    DELL     MD32xxi          0820  /dev/sdi 
[12:0:0:31]  disk    DELL     Universal Xport  0820  -        
[13:0:0:0]   disk    DELL     MD32xxi          0820  /dev/sdk 
[13:0:0:31]  disk    DELL     Universal Xport  0820  -        

# cat /proc/partitions 
   8      112 4544638484 sdh
   8      128 4544638484 sdi
   8      144 4544638484 sdj
   8      160 4544638484 sdk

# multipath -ll

# multipath -v2 -d
: md3200 (36d4ae5200083c20700001f86587fd4c3) undef DELL,MD32xxi
size=4.2T features='3 pg_init_retries 50 queue_if_no_path' hwhandler='1 rdac' wp=undef
`-+- policy='service-time 0' prio=11 status=undef
  |- 10:0:0:0 sdh 8:112 undef ready running
  |- 11:0:0:0 sdj 8:144 undef ready running
  |- 12:0:0:0 sdi 8:128 undef ready running
  `- 13:0:0:0 sdk 8:160 undef ready running

# dmsetup info -C
no relevant info. only LVM from local system
Comment 1 Kapetanakis Giannis 2019-01-30 13:03:19 UTC 
Created attachment 1525030 [details]
multipath -v3

multipath -v3 output
Comment 2 Ben Marzinski 2019-01-30 17:59:10 UTC 
If you look at the dmesg or journalctl output, I assume that you will see the kernel message like this:

device-mapper: table: table load rejected: not all devices are blk-mq request-stackable

This is because as of the 4.20 kernel, request-based device-mapper (which is what multipath uses for scsi devices) only works with block multiqueue devices.  Unfortunately, the legacy IO code wasn't removed from scsi devices until the 5.0 kernels. In 4.20, scsi devices support both the legacy IO path and blk-mq, and the fedora kernels are compiled to use the legacy IO path by default. You can change this by adding

scsi_mod.use_blk_mq=y

to the kernel commandline. This should fix your issue.  Otherwise, you can revert to a 4.19 kernel. Bug #1669235 is an identical bug for f29, using 4.20 kernels.
Comment 3 Kapetanakis Giannis 2019-01-31 10:06:29 UTC 
Yes I've seen this message on system logs.

The kernel option also worked. 
thanks :)
Comment 4 Ben Cotton 2019-05-02 19:55:28 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Ben Cotton 2019-05-28 23:39:40 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.