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:35:37 UTC
Description of problem:
# A striped raid
[root@host-117 ~]# lvcreate -i 10 --type raid4 -L 100M -n raid4 test
Using default stripesize 64.00 KiB.
Rounding size 100.00 MiB (25 extents) up to stripe boundary size 120.00 MiB (30 extents).
Number of stripes (10) must not exceed number of physical volumes (7)
# mirrored raid
[root@host-117 ~]# lvcreate -m 0 --type raid1 -L 100M -n raid1 test
--mirrors must be at least 1 with segment type raid1.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 11 --type raid1 -L 100M -n raid test
Only up to 10 mirrors in raid1 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 11 --type raid1 -L 100M -n raid1 test
Only up to 10 mirrors in raid1 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 10 --type raid1 -L 100M -n raid1 test
Only up to 10 mirrors in raid1 supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 9 --type raid1 -L 100M -n raid1 test
Insufficient suitable allocatable extents for logical volume raid1: 260 more required
[root@host-117 ~]# lvcreate -m 8 --type raid1 -L 100M -n raid1 test
Insufficient suitable allocatable extents for logical volume raid1: 234 more required
[root@host-117 ~]# lvcreate -m 7 --type raid1 -L 100M -n raid1 test
Insufficient suitable allocatable extents for logical volume raid1: 208 more required
[root@host-117 ~]# lvcreate -m 6 --type raid1 -L 100M -n raid1 test
Logical volume "raid1" created.
[root@host-117 ~]# lvcreate -m 0 --type mirror -L 100M -n mirror test
--mirrors must be at least 1 with segment type mirror.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 11 --type mirror -L 100M -n mirror test
Only up to 8 mirrors in mirror supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 10 --type mirror -L 100M -n mirror test
Only up to 8 mirrors in mirror supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 9 --type mirror -L 100M -n mirror test
Only up to 8 mirrors in mirror supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 8 --type mirror -L 100M -n mirror test
Only up to 8 mirrors in mirror supported currently.
Run `lvcreate --help' for more information.
[root@host-117 ~]# lvcreate -m 7 --type mirror -L 100M -n mirror test
Insufficient suitable allocatable extents for logical volume mirror: 200 more required
[root@host-117 ~]# lvcreate -m 6 --type mirror -L 100M -n mirror test
Logical volume "mirror" created.
[root@host-117 ~]# lvs -a -o +devices
LV VG Attr LSize Log Cpy%Sync Devices
mirror test mwi-a-m--- 100.00m [mirror_mlog] 100.00 mirror_mimage_0(0),mirror_mimage_1(0),mirror_mimage_2(0),mirror_mimage_3(0),mirror_mimage_4(0),mirror_mimage_5(0),mirror_mimage_6(0)
[mirror_mimage_0] test iwi-aom--- 100.00m /dev/sda1(26)
[mirror_mimage_1] test iwi-aom--- 100.00m /dev/sdb1(26)
[mirror_mimage_2] test iwi-aom--- 100.00m /dev/sdc1(26)
[mirror_mimage_3] test iwi-aom--- 100.00m /dev/sdd1(26)
[mirror_mimage_4] test iwi-aom--- 100.00m /dev/sde1(26)
[mirror_mimage_5] test iwi-aom--- 100.00m /dev/sdf1(26)
[mirror_mimage_6] test iwi-aom--- 100.00m /dev/sdg1(26)
[mirror_mlog] test lwi-aom--- 4.00m /dev/sdg1(51)
raid1 test rwi-a-r--- 100.00m 100.00 raid1_rimage_0(0),raid1_rimage_1(0),raid1_rimage_2(0),raid1_rimage_3(0),raid1_rimage_4(0),raid1_rimage_5(0),raid1_rimage_6(0)
[raid1_rimage_0] test iwi-aor--- 100.00m /dev/sda1(1)
[raid1_rimage_1] test iwi-aor--- 100.00m /dev/sdb1(1)
[raid1_rimage_2] test iwi-aor--- 100.00m /dev/sdc1(1)
[raid1_rimage_3] test iwi-aor--- 100.00m /dev/sdd1(1)
[raid1_rimage_4] test iwi-aor--- 100.00m /dev/sde1(1)
[raid1_rimage_5] test iwi-aor--- 100.00m /dev/sdf1(1)
[raid1_rimage_6] test iwi-aor--- 100.00m /dev/sdg1(1)
[raid1_rmeta_0] test ewi-aor--- 4.00m /dev/sda1(0)
[raid1_rmeta_1] test ewi-aor--- 4.00m /dev/sdb1(0)
[raid1_rmeta_2] test ewi-aor--- 4.00m /dev/sdc1(0)
[raid1_rmeta_3] test ewi-aor--- 4.00m /dev/sdd1(0)
[raid1_rmeta_4] test ewi-aor--- 4.00m /dev/sde1(0)
[raid1_rmeta_5] test ewi-aor--- 4.00m /dev/sdf1(0)
[raid1_rmeta_6] test ewi-aor--- 4.00m /dev/sdg1(0)
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
So I think this is just about considering whether the messages produced can be improved or not.
Comment 3Jonathan Earl Brassow
2017-07-27 21:56:20 UTC
(In reply to Alasdair Kergon from comment #2)
> So I think this is just about considering whether the messages produced can
> be improved or not.
yeah, might want to get back with reporter and ask specifically what they are looking for. Probably a few things that I can see that could use a touch-up. Low prio though.