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.
DescriptionCorey Marthaler
2016-08-26 23:14:59 UTC
Description of problem:
[root@host-117 ~]# lvcreate -i 64 --type raid10 -L 100M -n raid6 test
Using default stripesize 64.00 KiB.
Only up to 64 stripes in raid10 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -i 63 --type raid10 -L 100M -n raid6 test
Using default stripesize 64.00 KiB.
Only up to 64 stripes in raid10 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -i 33 --type raid10 -L 100M -n raid6 test
Using default stripesize 64.00 KiB.
Only up to 64 stripes in raid10 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -i 32 --type raid10 -L 100M -n raid6 test
Using default stripesize 64.00 KiB.
Rounding size 100.00 MiB (25 extents) up to stripe boundary size 128.00 MiB (32 extents).
Number of stripes (32) must not exceed number of physical volumes (7)
Version-Release number of selected component (if applicable):
lvm2-2.02.164-3.el7 BUILT: Wed Aug 24 05:20:41 CDT 2016
lvm2-libs-2.02.164-3.el7 BUILT: Wed Aug 24 05:20:41 CDT 2016
lvm2-cluster-2.02.164-3.el7 BUILT: Wed Aug 24 05:20:41 CDT 2016
Fix verified in the latest rpms.
3.10.0-497.el7.x86_64
lvm2-2.02.164-4.el7 BUILT: Wed Aug 31 08:47:09 CDT 2016
lvm2-libs-2.02.164-4.el7 BUILT: Wed Aug 31 08:47:09 CDT 2016
lvm2-cluster-2.02.164-4.el7 BUILT: Wed Aug 31 08:47:09 CDT 2016
device-mapper-1.02.133-4.el7 BUILT: Wed Aug 31 08:47:09 CDT 2016
device-mapper-libs-1.02.133-4.el7 BUILT: Wed Aug 31 08:47:09 CDT 2016
device-mapper-event-1.02.133-4.el7 BUILT: Wed Aug 31 08:47:09 CDT 2016
device-mapper-event-libs-1.02.133-4.el7 BUILT: Wed Aug 31 08:47:09 CDT 2016
device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT 2016
[root@host-117 ~]# lvcreate -i 64 --type raid10 -L 100M -n raid6 test
Using default stripesize 64.00 KiB.
Only up to 32 stripes in raid10 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -i 33 --type raid10 -L 100M -n raid6 test
Using default stripesize 64.00 KiB.
Only up to 32 stripes in raid10 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -i 32 --type raid10 -L 100M -n raid6 test
Using default stripesize 64.00 KiB.
Rounding size 100.00 MiB (25 extents) up to stripe boundary size 128.00 MiB (32 extents).
Number of stripes (32) must not exceed number of physical volumes (7)
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/RHBA-2016-1445.html