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.
Created attachment 1524182[details]
Output of lvextend from the above example.
If I extend a raid1 LV using lvextend, the newly allocated space in the two rimage devices isn't synced, just like if I had used the option --nosync.
As a result, a following raid check will report mismatches.
I am using Centos 7 with a 4.4 kernel-lt from ELRepo:
# rpm -q lvm2 device-mapper
lvm2-2.02.180-10.el7_6.2.x86_64
device-mapper-1.02.149-10.el7_6.2.x86_64
# uname -r
4.4.158-1.el7.elrepo.x86_64
Steps to Reproduce:
-------------------- 8< --------------------
# lvcreate -L1g --type raid1 -m 1 -n /dev/vg_sys/lv_test /dev/vg_sys
Logical volume "lv_test" created.
# lvs -a /dev/vg_sys/lv_test
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_test vg_sys rwi-a-r--- 1.00g 88.35
# lvs -a /dev/vg_sys/lv_test
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_test vg_sys rwi-a-r--- 1.00g 100.00
# lvextend -vvvv -L +1g /dev/vg_sys/lv_test
### (verbose output is added as attachment)
### sync percentage is immediately at 100%
# lvs -a /dev/vg_sys/lv_test
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_test vg_sys rwi-a-r--- 2.00g 100.00
# lvchange --syncaction check /dev/vg_sys/lv_test
# lvs -a /dev/vg_sys/lv_test
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_test vg_sys rwi-a-r--- 2.00g 6.25
# lvs -a /dev/vg_sys/lv_test
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_test vg_sys rwi-a-r-m- 2.00g 100.00
# lvs -o lv_path,lv_attr,lv_size,devices,raid_mismatch_count,lv_health_status /dev/vg_sys/lv_test
Path Attr LSize Devices Mismatches Health
/dev/vg_sys/lv_test rwi-a-r-m- 2.00g lv_test_rimage_0(0),lv_test_rimage_1(0) 2097152 mismatches exist
-------------------- 8< --------------------
Maybe the lvm2 / device-mapper version doesn't fit the kernel version?
Comment 2Heinz Mauelshagen
2019-08-28 21:30:20 UTC
*** This bug has been marked as a duplicate of bug 1671964 ***
Created attachment 1524182 [details] Output of lvextend from the above example. If I extend a raid1 LV using lvextend, the newly allocated space in the two rimage devices isn't synced, just like if I had used the option --nosync. As a result, a following raid check will report mismatches. I am using Centos 7 with a 4.4 kernel-lt from ELRepo: # rpm -q lvm2 device-mapper lvm2-2.02.180-10.el7_6.2.x86_64 device-mapper-1.02.149-10.el7_6.2.x86_64 # uname -r 4.4.158-1.el7.elrepo.x86_64 Steps to Reproduce: -------------------- 8< -------------------- # lvcreate -L1g --type raid1 -m 1 -n /dev/vg_sys/lv_test /dev/vg_sys Logical volume "lv_test" created. # lvs -a /dev/vg_sys/lv_test LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_test vg_sys rwi-a-r--- 1.00g 88.35 # lvs -a /dev/vg_sys/lv_test LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_test vg_sys rwi-a-r--- 1.00g 100.00 # lvextend -vvvv -L +1g /dev/vg_sys/lv_test ### (verbose output is added as attachment) ### sync percentage is immediately at 100% # lvs -a /dev/vg_sys/lv_test LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_test vg_sys rwi-a-r--- 2.00g 100.00 # lvchange --syncaction check /dev/vg_sys/lv_test # lvs -a /dev/vg_sys/lv_test LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_test vg_sys rwi-a-r--- 2.00g 6.25 # lvs -a /dev/vg_sys/lv_test LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_test vg_sys rwi-a-r-m- 2.00g 100.00 # lvs -o lv_path,lv_attr,lv_size,devices,raid_mismatch_count,lv_health_status /dev/vg_sys/lv_test Path Attr LSize Devices Mismatches Health /dev/vg_sys/lv_test rwi-a-r-m- 2.00g lv_test_rimage_0(0),lv_test_rimage_1(0) 2097152 mismatches exist -------------------- 8< -------------------- Maybe the lvm2 / device-mapper version doesn't fit the kernel version?