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 1144239[details]
Verbose output for the first case
Description of problem:
Version-Release number of selected component (if applicable):
LVM version: 2.02.130(2)-RHEL7 (2015-10-14)
Library version: 1.02.107-RHEL7 (2015-10-14)
Driver version: 4.33.0
How reproducible:
always
Steps to Reproduce:
CASE 1
vgcreate mypool /dev/sda
lvcreate mypool -T -l 100%PVS -n lvol001
Insufficient suitable allocatable extents found for logical volume lvol001.
It fails, yet it still creates a logical volume.
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lvol0 mypool -wi------- 100,00m
root rhel -wi-ao---- 17,51g
swap rhel -wi-ao---- 2,00g
CASE 2
vgcreate mypool /dev/sda /dev/sdb
lvcreate mypool -T -l 100%PVS -n lvol001
Fails as well, creating normal logical volume as well.
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lvol0 mypool -wi------- 100,00m
root rhel -wi-ao---- 17,51g
swap rhel -wi-ao---- 2,00g
CASE 3
vgcreate mypool /dev/sda /dev/sdb
lvcreate mypool -T -l 100%PVS -n lvol001 /dev/sda /dev/sdb
This case works exactly as I need which is, I specify devices which I need to be used for the thin pool, and exactly those devices are used.
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lvol001 mypool twi-a-tz-- 199,80g 0,00 0,43
root rhel -wi-ao---- 17,51g
swap rhel -wi-ao---- 2,00g
CASE 4
vgcreate mypool /dev/sda /dev/sdb /dev/sdc
lvcreate mypool -T -l 100%PVS -n lvol001 /dev/sda /dev/sdb
This is again the result I need.
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lvol001 mypool twi-a-tz-- 199,80g 0,00 0,43
root rhel -wi-ao---- 17,51g
swap rhel -wi-ao---- 2,00g
CASE 5
vgcreate mypool /dev/sda
lvcreate mypool -T -l 99%PVS -n lvol001 /dev/sda
Again does what I need it to do and creates proper thin pool.
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lvol001 mypool twi-a-tz-- 99,00g 0,00 0,43
root rhel -wi-ao---- 17,51g
swap rhel -wi-ao---- 2,00g
This behavior is unexpected for me and I'd think that in all cases this will provide me with the thin pool spread across provided devices, however in first two cases it fails to do so. It may be possible that I am using lvm tools wrong, but I am not sure how to achieve what I need in a different way which does not require me to create my own default sizes for data and metadata devices, or quess lvm2 heuristics of getting those sizes.
I'll attach the -vvv output for first two cases.
Thanks!
-Lukas
Comment 4Jonathan Earl Brassow
2017-07-27 20:50:12 UTC
need to know if this is fixed or what the next steps are.
Comment 6RHEL Program Management
2020-12-15 07:40:49 UTC
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.
Created attachment 1144239 [details] Verbose output for the first case Description of problem: Version-Release number of selected component (if applicable): LVM version: 2.02.130(2)-RHEL7 (2015-10-14) Library version: 1.02.107-RHEL7 (2015-10-14) Driver version: 4.33.0 How reproducible: always Steps to Reproduce: CASE 1 vgcreate mypool /dev/sda lvcreate mypool -T -l 100%PVS -n lvol001 Insufficient suitable allocatable extents found for logical volume lvol001. It fails, yet it still creates a logical volume. lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 mypool -wi------- 100,00m root rhel -wi-ao---- 17,51g swap rhel -wi-ao---- 2,00g CASE 2 vgcreate mypool /dev/sda /dev/sdb lvcreate mypool -T -l 100%PVS -n lvol001 Fails as well, creating normal logical volume as well. lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 mypool -wi------- 100,00m root rhel -wi-ao---- 17,51g swap rhel -wi-ao---- 2,00g CASE 3 vgcreate mypool /dev/sda /dev/sdb lvcreate mypool -T -l 100%PVS -n lvol001 /dev/sda /dev/sdb This case works exactly as I need which is, I specify devices which I need to be used for the thin pool, and exactly those devices are used. lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol001 mypool twi-a-tz-- 199,80g 0,00 0,43 root rhel -wi-ao---- 17,51g swap rhel -wi-ao---- 2,00g CASE 4 vgcreate mypool /dev/sda /dev/sdb /dev/sdc lvcreate mypool -T -l 100%PVS -n lvol001 /dev/sda /dev/sdb This is again the result I need. lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol001 mypool twi-a-tz-- 199,80g 0,00 0,43 root rhel -wi-ao---- 17,51g swap rhel -wi-ao---- 2,00g CASE 5 vgcreate mypool /dev/sda lvcreate mypool -T -l 99%PVS -n lvol001 /dev/sda Again does what I need it to do and creates proper thin pool. lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol001 mypool twi-a-tz-- 99,00g 0,00 0,43 root rhel -wi-ao---- 17,51g swap rhel -wi-ao---- 2,00g This behavior is unexpected for me and I'd think that in all cases this will provide me with the thin pool spread across provided devices, however in first two cases it fails to do so. It may be possible that I am using lvm tools wrong, but I am not sure how to achieve what I need in a different way which does not require me to create my own default sizes for data and metadata devices, or quess lvm2 heuristics of getting those sizes. I'll attach the -vvv output for first two cases. Thanks! -Lukas