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:
Thin pool target has limitation in the use of external origin device size.
If the chunk size is not a power of 2 (i.e. data device is stripe across 3 disks with 64k chunk - combined into 192k stripe/pool chunk_size/block_size) and external origin is just aligned to MB (i.e. 4M extent boundary) it cannot be used - since the last 'unaligned' chunk is not provisioned so any write to the end of thin volume which uses this external is lost.
The latest version of lvm2 prohibits this combination (so can't be easily used to reproduce this bug, unless patching code)
Once the thin pool target is upgraded to support this combination,
new property could be used to enable support for this.
The bug could be also related to Bug 1030411.
Version-Release number of selected component (if applicable):
thin pool target version 1.10
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
This bug is mainly for tracking kernel bug in target.
Lvm2 currently detects unsupported sizes and doesn't allow to active/create such combination of external origin and thin pool.
lvm2 test suite:
https://git.fedorahosted.org/cgit/lvm2.git/tree/test/shell/lvcreate-thin-external.sh
<<<
vgcreate $vg -s 64K $(cat DEVICES)
# Test validation for external origin being multiple of thin pool chunk size
lvcreate -L10M -T $vg/pool192 -c 192k
lvcreate -an -pr -Zn -l1 -n $lv1 $vg
not lvcreate -s $vg/$lv1 --thinpool $vg/pool192
>>>
VG uses 64K extent - pool has 192K chunks and external origin has just one 64K extent - this will not work in current thinpool driver and lvm2 must not allow to use this combination. More combination tests like this are possible.
(In reply to Zdenek Kabelac from comment #3)
> Lvm2 currently detects unsupported sizes and doesn't allow to active/create
> such combination of external origin and thin pool.
Moving this to 7.1.
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.
https://rhn.redhat.com/errata/RHSA-2015-0290.html