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.
Description of problem:
When creating a PV with '--metadatacopies 2', the calculation of "not usable" space for pvdisplay is incorrect.
In file lib/display/display.c, the following comparison is made:
if (pv->size > data_size + pv->pe_start) {
pvsize = pv->size;
unusable = pvsize - data_size;
}
But if there are two copies of metadata, this will always yield a "not usable" amount equivalent to the space allocated to the two metadata copies. It seems that there should be a test for pv_mda_count, and if equal to two, subtract (pv_mda_size+pv->pe_start) from the unusable amount.
[pv_mda_size is the smallest of the two metadata areas. But that seems sufficient: the most efficient is for both metadata areas to be the same size. But the first metadata space may be rounded up to preserve alignment. The alternative is to check for the size of the second metadata copy. But I don't know if it is as readily available, and besides, it wouldn't help if it is bigger than the first metadata copy.]
As for the inconsistency: even for one metadata copy, the 'not usable' space includes the space of the one metadata copy. It seems that pv->pe_start should be subtracted from the "not usable" space.
[Also, I am not sure when the 'else' clause gets triggered, other than when pv->size is equal to the sum of data_size and pv->pe_start, and the not usable space is zero.]
Version-Release number of selected component (if applicable):
Current master branch, after lvm2 Release 2.03.15
How reproducible:
Steps to Reproduce:
1. Create PV with '--metadatacopies 2'
2. Create VG
3. Run pvdisplay
Actual results:
Shows "not usable" amount that does not correspond to not usable amount
Expected results:
Additional info:
Comment 3RHEL Program Management
2023-09-23 15:52:46 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4RHEL Program Management
2023-09-23 15:57:51 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: When creating a PV with '--metadatacopies 2', the calculation of "not usable" space for pvdisplay is incorrect. In file lib/display/display.c, the following comparison is made: if (pv->size > data_size + pv->pe_start) { pvsize = pv->size; unusable = pvsize - data_size; } But if there are two copies of metadata, this will always yield a "not usable" amount equivalent to the space allocated to the two metadata copies. It seems that there should be a test for pv_mda_count, and if equal to two, subtract (pv_mda_size+pv->pe_start) from the unusable amount. [pv_mda_size is the smallest of the two metadata areas. But that seems sufficient: the most efficient is for both metadata areas to be the same size. But the first metadata space may be rounded up to preserve alignment. The alternative is to check for the size of the second metadata copy. But I don't know if it is as readily available, and besides, it wouldn't help if it is bigger than the first metadata copy.] As for the inconsistency: even for one metadata copy, the 'not usable' space includes the space of the one metadata copy. It seems that pv->pe_start should be subtracted from the "not usable" space. [Also, I am not sure when the 'else' clause gets triggered, other than when pv->size is equal to the sum of data_size and pv->pe_start, and the not usable space is zero.] Version-Release number of selected component (if applicable): Current master branch, after lvm2 Release 2.03.15 How reproducible: Steps to Reproduce: 1. Create PV with '--metadatacopies 2' 2. Create VG 3. Run pvdisplay Actual results: Shows "not usable" amount that does not correspond to not usable amount Expected results: Additional info: