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.
Cause:
Previously some lvm2app functions were returning values in sectors instead of bytes.
Consequence:
All return values from lvm2app should be in bytes, thus using sector values as byte values were giving incorrect results.
Fix:
Return values from lvm2app have been validated to return byte values.
Result:
Values for origin_size, vg_extent_size, stripe_size, region_size, chunk_size, seg_start, pvseg_size are now properly reported in bytes.
Description of problem:
The lvm2app library reports the stripe size of volumes
incorrectly.
~# lvs --version
LVM version: 2.02.98(2) (2012-10-15)
Library version: 1.02.77 (2012-10-15)
Driver version: 4.23.0
For example if I create a volume with 2 stripes of 128k:
~# lvcreate -i 2 -I 128 --extents 100 vg1
Logical volume "lvol0" created
The lvs command gets it right:
~# lvs -o +stripe_size
LV VG Attr LSize Pool Data% Move Log Copy% Convert Stripe
lvol0 vg1 -wi-a---- 100.00m 128.00k
However, the number from the library is as follows:
value = lvm_lvseg_get_property(lvm_lvseg, "stripesize");
if (value.is_valid)
qDebug() << "Stripe size: " << value.value.integer;
Result:
Stripe size: 256
The library seems to be reporting the number of sectors since
256 * 512 = 131072 bytes which is 128k.
The error occures with any stripe size;
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.
http://rhn.redhat.com/errata/RHBA-2013-1704.html
Description of problem: The lvm2app library reports the stripe size of volumes incorrectly. ~# lvs --version LVM version: 2.02.98(2) (2012-10-15) Library version: 1.02.77 (2012-10-15) Driver version: 4.23.0 For example if I create a volume with 2 stripes of 128k: ~# lvcreate -i 2 -I 128 --extents 100 vg1 Logical volume "lvol0" created The lvs command gets it right: ~# lvs -o +stripe_size LV VG Attr LSize Pool Data% Move Log Copy% Convert Stripe lvol0 vg1 -wi-a---- 100.00m 128.00k However, the number from the library is as follows: value = lvm_lvseg_get_property(lvm_lvseg, "stripesize"); if (value.is_valid) qDebug() << "Stripe size: " << value.value.integer; Result: Stripe size: 256 The library seems to be reporting the number of sectors since 256 * 512 = 131072 bytes which is 128k. The error occures with any stripe size;