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.
Created attachment 967751[details]
Testcase script
Description of problem:
This is a piece of the puzzle of bug #1167240 and very urgent for RHEV 3.5 GA.
parted does some weird things in a specific storage setup (described below).
Version-Release number of selected component (if applicable):
# rpm -q parted device-mapper-multipath lvm2 kernel redhat-release-server
parted-2.1-25.el6.x86_64
device-mapper-multipath-0.4.9-80.el6_6.1.x86_64
lvm2-2.02.111-2.el6.x86_64
kernel-2.6.32-504.el6.x86_64
kernel-2.6.32-504.1.3.el6.x86_64
redhat-release-server-6Server-6.6.0.2.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
0. Create a VM with two disks
One is the installation destination
Second is used for testing (attach over IDE bus!)
1. Install clean 6.6 onto the first disk
2. Configure:
yum install device-mapper-multipath parted lvm2
mpathconf --enable --find_multipaths y
service multipathd start
# Use the attached script and run:
# (sda should be the second disk)
bash stacktest.sh /dev/sda
3.
Actual results:
parted has problems with the mpath partitions:
…
+ lvcreate -L 3 -n TESTLV TESTVG
Rounding up size to full physical extent 4.00 MiB
Logical volume "TESTLV" created
+ partprobe
device-mapper: remove ioctl on mpathap3 failed: Device or resource busy
Warning: parted was unable to re-read the partition table on /dev/mapper/mpatha (Device or resource busy). This means Linux won't know anything about the modifications you made.
device-mapper: create ioctl on mpathap3 failed: Device or resource busy
device-mapper: remove ioctl on mpathap3 failed: Device or resource busy
Warning: WARNING: the kernel failed to re-read the partition table on /dev/vda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot.
+ lvremove -f TESTVG/TESTLV
Logical volume "TESTLV" successfully removed
…
Expected results:
parted handles the partitions correctly:
…
+ lvcreate -L 3 -n TESTLV TESTVG
Rounding up size to full physical extent 4.00 MiB
Logical volume "TESTLV" created
+ partprobe
+ lvremove -f TESTVG/TESTLV
Logical volume "TESTLV" successfully removed
…
Additional info:
According to my understanding there might be a few pacthes missing, see also
bug 1167240 comment 47.
It seems that the multipath device is necessary, if you comment out that part of the stack, then the test passes.
It seems that the test also passes when you comment out the LV creation (and usage).
I tried to reproduce with a 6.6 install on a VM using ide bus drives and wasn't able to get multipath to cooperate. I did, however, reproduce part of it without the multipath layer and it is actually working as expected.
See comment 49 on bug 1167240.
I'll wait until next week to close this, but it comes down to calling partprobe at the wrong time and not specifying the device (when you don't it tries all the devices whether or not they are busy).