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 1842744 - lvcreate aborts with assertion Assertion `to_go <= pva->count' failed
Summary: lvcreate aborts with assertion Assertion `to_go <= pva->count' failed
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1839301
TreeView+ depends on / blocked
 
Reported: 2020-06-02 03:00 UTC by Raghavendra Talur
Modified: 2021-09-03 12:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-12 05:37:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Raghavendra Talur 2020-06-02 03:00:20 UTC 
Description of problem:

While trying to create a LV on a VG, lvcreate aborts with an assertion.


Version-Release number of selected component (if applicable):
# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.8 (Maipo)
# rpm -qa | grep lvm
lvm2-libs-2.02.186-7.el7_8.1.x86_64
lvm2-2.02.186-7.el7_8.1.x86_64


How reproducible:
Always when the size of the lv being created is close to the free size in the VG.

Steps to Reproduce:
1. Create a VG and create few LVs which consume some space on it
2. Try to create a LV which consumes space close to but lesser than the free space on the VG


Actual results:
The creation should succeed.

Expected results:
lvcreate aborts with an assert.

Additional info:
Comment 5 Heinz Mauelshagen 2020-07-15 16:12:43 UTC 
Raghavendra,

I tried this with 

LVM version:     2.02.187(2)-RHEL7 (2020-03-24)
  Library version: 1.02.170-RHEL7 (2020-03-24)
  Driver version:  4.37.1
  Configuration:   ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix
=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedi
r=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-default-dm-run-dir=/run --with-default-run-dir=/run/lvm --with-default-pid-dir=
/run --with-default-locking-dir=/run/lock/lvm --with-usrlibdir=/usr/lib64 --enable-lvm1_fallback --enable-fsadm --with-pool=internal --enable-write_install --with-user= 
--with-group= --with-device-uid=0 --with-device-gid=6 --with-device-mode=0660 --enable-pkgconfig --enable-applib --enable-cmdlib --enable-dmeventd --enable-blkid_wiping 
--enable-python2-bindings --with-cluster=internal --with-clvmd=corosync --enable-cmirrord --with-udevdir=/usr/lib/udev/rules.d --enable-udev_sync --with-thin=internal --
enable-lvmetad --with-cache=internal --enable-lvmpolld --enable-lvmlockd-dlm --enable-lvmlockd-sanlock --enable-dmfilemapd


Created VG, allocated LVs and tried variations of free space minus a few extents for the last one to trigger the assertion -> not triggered.

Can you provide your simplest reproducer?
Comment 6 Raghavendra Talur 2020-08-20 19:00:33 UTC 
Unfortunately I don't have any reproducer simpler than that described in the original description. 
I agree with the current resolution of the bug and we can reopen if we start seeing this again in our setups.
Comment 7 Zdenek Kabelac 2021-02-02 22:29:56 UTC 
Fixed upstream:

https://www.redhat.com/archives/lvm-devel/2020-September/msg00062.html
https://www.redhat.com/archives/lvm-devel/2021-January/msg00009.html
Note You need to log in before you can comment on or make changes to this bug.