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: | lvm2 | Assignee: | 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.3 | Keywords: | MigratedToJIRA |
| Target Milestone: | rc | Flags: | 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
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) 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. 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. |