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 1479778 [details]
lvcreate_vvvv

raid4 creation occasionally fails with internal error, seems to be only happening on "clean" pv with specific region and lv size.

# lvcreate  --type raid4 -R 512.00k -i 5 -n takeover -L 2.75G centipede2
  Using default stripesize 64.00 KiB.
  Rounding size 2.75 GiB (704 extents) up to stripe boundary size 2.75 GiB(705 extents).
  device-mapper: reload ioctl on  (253:14) failed: Invalid argument
  Failed to activate new LV.
  Internal error: Removing still active LV centipede2/takeover_rmeta_0.
  Manual intervention may be required to remove abandoned LV(s) before retrying.


This is not easily reproducible, and seems to be happening only when the same volume was previously removed and then attempted to be created again.

I managed to trigger this with region size of 256k or 512k. Running the script attached should hit this after few iterations. 


Reproducer:
(run multiple times if error does not appear)

  pvcreate --zero y /dev/sd{a..j}1
  vgcreate vg /dev/sd{a..j}1
  lvcreate  --type raid4 -R 512.00k -i 5 -n lv -L 2.75G vg
  lvremove -y vg/lv
  lvcreate  --type raid4 -R 512.00k -i 5 -n lv -L 2.75G vg
  lvremove -y vg/lv
  vgremove -y vg


kernel-3.10.0-938.el7.x86_64
lvm2-2.02.180-6.el7.x86_64

Created attachment 1479779 [details]
reproducer

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.