Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1382860 - what does stripesize have to do with thin/cache pool creation?
what does stripesize have to do with thin/cache pool creation?
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2 (Show other bugs)
7.3
x86_64 Linux
unspecified Severity low
: rc
: ---
Assigned To: Zdenek Kabelac
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-10-07 18:20 EDT by Corey Marthaler
Modified: 2018-04-10 11:19 EDT (History)
9 users (show)

See Also:
Fixed In Version: lvm2-2.02.176-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 11:18:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0853 None None None 2018-04-10 11:19 EDT

  None (edit)
Description Corey Marthaler 2016-10-07 18:20:13 EDT
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 05:09:13 EST
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 06:36:37 EST
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 18:34:13 EST
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 11:18:32 EDT
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.