Bug 2203265
| Summary: | protection against splitting off mirror legs during up conversion appears to be missing now when sync is close to completion with fast nvme devices | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Heinz Mauelshagen <heinzm> |
| lvm2 sub component: | Mirroring and RAID | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED MIGRATED | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac |
| Version: | 9.3 | Keywords: | MigratedToJIRA, Triaged |
| 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:03:10 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-11 16:49:40 UTC
This appears to only happen with fast nvme devices. I haven't been able to reproduce this with SSDs. Also, if I bump the size of the mirror way up with the nvme devices, then I will see the "Unable to split mirror mirror_sanity/fs_to_mirror that is not in-sync." messages again. So this appears to be a timing issue where LVM thinks the sync is complete, or close to complete, but it's not really. (In reply to Corey Marthaler from comment #1) > This appears to only happen with fast nvme devices. I haven't been able to > reproduce this with SSDs. Also, if I bump the size of the mirror way up with > the nvme devices, then I will see the "Unable to split mirror > mirror_sanity/fs_to_mirror that is not in-sync." messages again. > > So this appears to be a timing issue where LVM thinks the sync is complete, > or close to complete, but it's not really. So it seems. FYI: we've seen similar issues with dm-raid on (small) LVs backed by fast PVs whch have been fixed a few years ago. No reproducer in VM here (virtio-scsi -> host thin -> host PCIe4 NVMe): # lvconvert -y --ty mirror -m1 t/t&lvconvert -y --splitmirrors 1 --name n t/t [1] 5089 Logical volume t/t being converted. Unable to split mirror t/t that is not in-sync. t/t: Converted: 75.00% # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root rhel_vm45 -wi-ao---- <17.00g swap rhel_vm45 -wi-ao---- 2.00g t t mwi-a-m--- 128.00m [t_mlog] 100.00 # lvconvert -m0 t t/t: Converted: 100.00% /t Logical volume t/t converted. [root@vm45 ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root rhel_vm45 -wi-ao---- <17.00g swap rhel_vm45 -wi-ao---- 2.00g t t -wi-a----- 128.00m # lvconvert -y --ty mirror -m1 t/t&sleep 0.1;lvconvert -y --splitmirrors 1 --name n t/t [2] 5404 Logical volume t/t being converted. [1] Done lvconvert -y --ty mirror -m1 t/t Unable to split mirror t/t that is not in-sync. t/t: Converted: 71.88% 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. |