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.
Bug 1382860 - what does stripesize have to do with thin/cache pool creation?
Summary: what does stripesize have to do with thin/cache pool creation?
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-07 22:20 UTC by Corey Marthaler
Modified: 2021-09-03 12:49 UTC (History)
9 users (show)

Fixed In Version: lvm2-2.02.176-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 15:18:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0853 0 None None None 2018-04-10 15:19:55 UTC

Description Corey Marthaler 2016-10-07 22:20:13 UTC 
Description of problem:
Looks like I should have tested other volume types when filing bug 1366745.

[root@host-119 ~]# lvcreate  --yes --type cache-pool -L 500M test/cpool
  Using default stripesize 64.00 KiB.
  Logical volume "cpool" created.

[root@host-119 ~]# lvcreate  --yes --type cache -L 500M test/cpool
  Using default stripesize 64.00 KiB.
  Logical volume "lvol1" created.

[root@host-119 ~]# lvcreate  --yes --type thin-pool -L 500M test/tpool
  Using default stripesize 64.00 KiB.
  Logical volume "tpool" created.


Version-Release number of selected component (if applicable):
lvm2-2.02.166-1.el7    BUILT: Wed Sep 28 02:26:52 CDT 2016
lvm2-libs-2.02.166-1.el7    BUILT: Wed Sep 28 02:26:52 CDT 2016
lvm2-cluster-2.02.166-1.el7    BUILT: Wed Sep 28 02:26:52 CDT 2016
device-mapper-1.02.135-1.el7    BUILT: Wed Sep 28 02:26:52 CDT 2016
Comment 2 Zdenek Kabelac 2016-12-15 10:09:13 UTC 
Well - the message got there because of some validation unification for raid code.  I agree the message should be not displayed when just ordinary linear LV is created  (--stripes 1)  (linear is just sub-case of default stripe type being created)
Comment 5 Zdenek Kabelac 2017-11-27 11:36:37 UTC 
Addressed primarily with upstream patch:

https://www.redhat.com/archives/lvm-devel/2017-November/msg00085.html

(But few more surrouding patches were added as well to improve stripe handling on cmdline)
Comment 7 Corey Marthaler 2017-12-08 23:34:13 UTC 
Fix verified in the latest rpms.

3.10.0-811.el7.x86_64

lvm2-2.02.176-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
lvm2-libs-2.02.176-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
lvm2-cluster-2.02.176-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
lvm2-lockd-2.02.176-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
lvm2-python-boom-0.8.1-5.el7    BUILT: Wed Dec  6 04:15:40 CST 2017
cmirror-2.02.176-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
device-mapper-1.02.145-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
device-mapper-libs-1.02.145-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
device-mapper-event-1.02.145-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
device-mapper-event-libs-1.02.145-5.el7    BUILT: Wed Dec  6 04:13:07 CST 2017
device-mapper-persistent-data-0.7.3-2.el7    BUILT: Tue Oct 10 04:00:07 CDT 2017



[root@host-117 ~]# lvcreate  --yes --type cache-pool -L 500M test/cpool
  Logical volume "cpool" created.
[root@host-117 ~]# lvcreate  --yes --type cache -L 500M test/cpool
  Logical volume "lvol1" created.
[root@host-117 ~]# lvcreate  --yes --type thin-pool -L 500M test/tpool
  Thin pool volume with chunk size 64.00 KiB can address at most 15.81 TiB of data.
  Logical volume "tpool" created.
Comment 10 errata-xmlrpc 2018-04-10 15:18:32 UTC 
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://access.redhat.com/errata/RHEA-2018:0853
Note You need to log in before you can comment on or make changes to this bug.