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.

Bug 2210349

Summary: raid --minrecoveryrate flag either doesn't work at all with lvcreate, or should tell the user what the maximum is
Product: Red Hat Enterprise Linux 9 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: LVM Team <lvm-team>
lvm2 sub component: Mirroring and RAID QA Contact: cluster-qe <cluster-qe>
Status: CLOSED MIGRATED Docs Contact:
Severity: low    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac
Version: 9.3Keywords: MigratedToJIRA
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-23 19:09:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2023-05-26 18:25:20 UTC 
Description of problem:

[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 64 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.
[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 32 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.
[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 16 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.
[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 8 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.
[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 4 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.
[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 2 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.
[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 1 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.

[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 1b -n mylv2 myvg 
  Size is not a multiple of 512. Try using 0 or 512.
  Invalid argument for --minrecoveryrate: 1b
  Error during parsing of command line.

[root@virt-521 ~]# lvcreate --type raid10 -i 2 -m 1 -L 10G --minrecoveryrate 512 -n mylv2 myvg 
  Using default stripesize 64.00 KiB.
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.

[root@virt-521 ~]# lvcreate --type raid1 -m 1 -L 10G --minrecoveryrate 512 -n mylv2 myvg 
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.
[root@virt-521 ~]# lvcreate --type raid1 -m 1 -L 10G --minrecoveryrate 4kb -n mylv2 myvg 
  Minimum recovery rate cannot be higher than maximum.
  Run `lvcreate --help' for more information.



Version-Release number of selected component (if applicable):
kernel-5.14.0-312.el9    BUILT: Thu May 11 08:04:19 PM CEST 2023
lvm2-2.03.21-2.el9    BUILT: Thu May 25 12:03:04 AM CEST 2023
lvm2-libs-2.03.21-2.el9    BUILT: Thu May 25 12:03:04 AM CEST 2023
Comment 1 Corey Marthaler 2023-05-26 18:29:14 UTC 
This works w/ lvchange however.

[root@virt-521 ~]# lvs -a -o +devices,raid_min_recovery_rate,raid_max_recovery_rate
  LV              VG   Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices                           MinSync MaxSync
  mylv            myvg rwi-a-r--- 10.00g                                    100.00           mylv_rimage_0(0),mylv_rimage_1(0)                
  [mylv_rimage_0] myvg iwi-aor--- 10.00g                                                     /dev/sda(1)                                      
  [mylv_rimage_1] myvg iwi-aor--- 10.00g                                                     /dev/sdb(1)                                      
  [mylv_rmeta_0]  myvg ewi-aor---  4.00m                                                     /dev/sda(0)                                      
  [mylv_rmeta_1]  myvg ewi-aor---  4.00m                                                     /dev/sdb(0)                                      
[root@virt-521 ~]# lvchange --minrecoveryrate 64 myvg/mylv
  Logical volume myvg/mylv changed.
[root@virt-521 ~]# lvs -a -o +devices,raid_min_recovery_rate,raid_max_recovery_rate
  LV              VG   Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices                           MinSync MaxSync
  mylv            myvg rwi-a-r--- 10.00g                                    100.00           mylv_rimage_0(0),mylv_rimage_1(0)      64        
  [mylv_rimage_0] myvg iwi-aor--- 10.00g                                                     /dev/sda(1)                                      
  [mylv_rimage_1] myvg iwi-aor--- 10.00g                                                     /dev/sdb(1)                                      
  [mylv_rmeta_0]  myvg ewi-aor---  4.00m                                                     /dev/sda(0)                                      
  [mylv_rmeta_1]  myvg ewi-aor---  4.00m                                                     /dev/sdb(0)                                      
[root@virt-521 ~]# lvchange --maxrecoveryrate 128 myvg/mylv
  Logical volume myvg/mylv changed.
[root@virt-521 ~]# lvs -a -o +devices,raid_min_recovery_rate,raid_max_recovery_rate
  LV              VG   Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices                           MinSync MaxSync
  mylv            myvg rwi-a-r--- 10.00g                                    100.00           mylv_rimage_0(0),mylv_rimage_1(0)      64     128
  [mylv_rimage_0] myvg iwi-aor--- 10.00g                                                     /dev/sda(1)                                      
  [mylv_rimage_1] myvg iwi-aor--- 10.00g                                                     /dev/sdb(1)                                      
  [mylv_rmeta_0]  myvg ewi-aor---  4.00m                                                     /dev/sda(0)                                      
  [mylv_rmeta_1]  myvg ewi-aor---  4.00m                                                     /dev/sdb(0)
Comment 3 RHEL Program Management 2023-09-23 19:04:03 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4 RHEL Program Management 2023-09-23 19:09:07 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.