Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1311659

Summary: Add multipath option to disable kpartx partition creation
Product: Red Hat Enterprise Linux 7 Reporter: Ben Marzinski <bmarzins>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Lin Li <lilin>
Severity: unspecified Docs Contact: Steven J. Levine <slevine>
Priority: high    
Version: 7.2CC: agk, bmarzins, dwysocha, heinzm, lherbolt, lilin, msnitzer, prajnoha, prockai, rbalakri, salmy, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: device-mapper-multipath-0.4.9-91.el7 Doc Type: Enhancement
Doc Text:
New `skip_kpartx` configuration option to allow skipping `kpartx` partition creation The `skip_kpartx` option has been added to the defaults, devices, and multipaths sections of the `multipath.conf` file. When this option is set to `yes`, multipath devices that are configured with `skip_kpartx` will not have any partition devices created for them. This allows users to create a multipath device without creating partitions, even if the device has a partition table. The default value of this option is `no`.
 Story Points: ---
Clone Of: 1310320
: 1386360 (view as bug list) Environment:
Last Closed: 2016-11-04 08:18:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1310320    
Bug Blocks: 1386360, 1388229    

Comment 1 Ben Marzinski 2016-06-03 15:49:25 UTC 
I've added an option "skip_kpartx" to the defaults, devices, and multipaths section of multipath.conf. Setting this on a device will disable kpartx handling. This works using udev rules and the DM_SUBSYSTEM_UDEV_FLAG1, as I explained above.
Comment 2 Lin Li 2016-06-30 14:57:06 UTC 
Verified on device-mapper-multipath-0.4.9-91.el7
#man multipath.conf
defaults section
       skip_kpartx      If set to yes , kpartx will not automatically create partitions on the device. The default is no

multipaths section
       The following attributes are optional; if not set the default values are taken from the defaults or devices section:
              skip_kpartx

devices section
       The following attributes are optional; if not set the default values are taken from the defaults section:
              skip_kpartx
Comment 4 Lin Li 2016-07-07 12:59:53 UTC 
Verified on device-mapper-multipath-0.4.9-91.el7
1. #edit /etc/multipath.conf
defaults {
        find_multipaths yes
        user_friendly_names yes
        prio weightedpath
        prio_args "wwn 0x20000000c9a02834:.*:.*:.* 30"
        skip_kpartx yes
}

2.# multipath -r
reload: 360a98000324669436c2b45666c567942 undef NETAPP  ,LUN             
size=20G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:0   sdb  8:16   active ready running
| `- 6:0:1:0   sdz  65:144 active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:0   sdj  8:144  active ready running
  `- 6:0:0:0   sdr  65:16  undef ready running
reload: 360a98000324669436c2b45666c567944 undef NETAPP  ,LUN             
size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:1   sdc  8:32   active ready running
| `- 6:0:1:1   sdaa 65:160 active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:1   sdk  8:160  active ready running
  `- 6:0:0:1   sds  65:32  undef ready running
reload: 360a98000324669436c2b45666c567946 undef NETAPP  ,LUN             
size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:2   sdd  8:48   active ready running
| `- 6:0:1:2   sdab 65:176 active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:2   sdl  8:176  active ready running
  `- 6:0:0:2   sdt  65:48  undef ready running
reload: 360a98000324669436c2b45666c596e65 undef NETAPP  ,LUN             
size=5.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:225 sdi  8:128  active ready running
| `- 6:0:1:225 sdag 66:0   active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:225 sdq  65:0   active ready running
  `- 6:0:0:225 sdy  65:128 undef ready running
reload: 360a98000324669436c2b45666c567948 undef NETAPP  ,LUN             
size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:3   sde  8:64   active ready running
| `- 6:0:1:3   sdac 65:192 active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:3   sdm  8:192  active ready running
  `- 6:0:0:3   sdu  65:64  undef ready running
reload: 360a98000324669436c2b45666c56794a undef NETAPP  ,LUN             
size=2.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:4   sdf  8:80   active ready running
| `- 6:0:1:4   sdad 65:208 active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:4   sdn  8:208  active ready running
  `- 6:0:0:4   sdv  65:80  undef ready running
reload: 360a98000324669436c2b45666c596f54 undef NETAPP  ,LUN             
size=5.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:5   sdg  8:96   active ready running
| `- 6:0:1:5   sdae 65:224 active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:5   sdo  8:224  active ready running
  `- 6:0:0:5   sdw  65:96  undef ready running
reload: 360a98000324669436c2b45666c596f56 undef NETAPP  ,LUN             
size=5.0G features='3 queue_if_no_path pg_init_retries 50' hwhandler='0' wp=undef
|-+- policy='service-time 0' prio=50 status=undef
| |- 5:0:0:6   sdh  8:112  active ready running
| `- 6:0:1:6   sdaf 65:240 active ready running
`-+- policy='service-time 0' prio=10 status=undef
  |- 5:0:1:6   sdp  8:240  active ready running
  `- 6:0:0:6   sdx  65:112 undef ready running
Comment 5 Lin Li 2016-07-07 13:01:42 UTC 
change to verified according to comment 2 and comment 4.
Comment 7 errata-xmlrpc 2016-11-04 08:18:18 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2536.html