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 thin pool, its notifies you that the thin pool was created AND a volume called lvol0 - which isnt actually created
Version-Release number of selected component (if applicable):
lvm2-2.02.100-8.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Install RHEL6.5 and yum update
2. create a thin pool
3. observe the, incorrect, additional message
Actual results:
Thin pool is created and you are notified that a lvol0 was also created, which is wasnt
Expected results:
Dont tell me lvol0 was created in addition to my thin pool
Additional info:
[root@thin-tests ~]# lvs
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
rootvol myvg -wi-ao---- 7.31g
[root@thin-tests ~]# lvcreate -l 46 --type thin-pool --thinpool tp_pool myvg
Logical volume "lvol0" created
Logical volume "tp_pool" created
[root@thin-tests ~]# lvs
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
rootvol myvg -wi-ao---- 7.31g
tp_pool myvg twi-a-tz-- 1.44g 0.00
[root@thin-tests ~]# rpm -q lvm2
lvm2-2.02.100-8.el6.x86_64
Created lvol0 is volume used as a 'spare' LV for a possible thin pool recovery.
It's just later renamed to lvol0_pmspare and as such it is hidden volume.
(lvs -a is needed)
However we are considering to remove this creation message - it's not yet defined.
Anyway - it's not a bug - it's rather informational noise which needs some cleaning.
It's not that easy to decide.
Since anywhere during creation process the machine could be turned off/crash,
it might happen you would end-up after reboot with a 'lvol0' volume
and you would have no idea who was creating it and why it is there
(thus probably reporting even bug on lvm2....)
So while we are printing info about creation of lvol0 - we make a user aware
there was this volume created and it's temporarily present.
But we do not inform about later usage of this volume as a thin pool spare LV.
Which might be another solution for this problem - to just print notice,
lvol0 is used is pool metadata spare LV.