Bug 213759
Summary: | regression: mirror sync log not being properly zero'ed out | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Corey Marthaler <cmarthal> |
Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | CC: | dwysocha, jbrassow, mbroz, prockai |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHBA-2007-0287 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-05-08 00:12:27 UTC | Type: | --- |
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
2006-11-02 21:18:57 UTC
If I run 'lvchange --resync <mirror>' that will cause the mirror to start sync'ing from 0.0% like it's supposed to without the quick jump. Also, it always appears to start at the same percent for a given mirror size: [root@link-08 ~]# lvcreate -m 1 -n mirror -L 75G vg Logical volume "mirror" created [root@link-08 ~]# lvs LV VG Attr LSize Origin Snap% Move Log Copy% mirror vg mwi-a- 75.00G mirror_mlog 84.04 [root@link-08 ~]# lvremove -f vg Logical volume "mirror" successfully removed [root@link-08 ~]# lvcreate -m 1 -n mirror -L 75G vg Logical volume "mirror" created [root@link-08 ~]# lvs LV VG Attr LSize Origin Snap% Move Log Copy% mirror vg mwi-a- 75.00G mirror_mlog 84.04 [root@link-08 ~]# lvremove -f vg Logical volume "mirror" successfully removed [root@link-08 ~]# lvcreate -m 1 -n mirror -L 75G vg Logical volume "mirror" created [root@link-08 ~]# lvs LV VG Attr LSize Origin Snap% Move Log Copy% mirror vg mwi-a- 75.00G mirror_mlog 84.05 Comment #2 means that the same patern is being written to disk every time rather than the device not actually being cleared. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering. This request is not yet committed for inclusion in release. http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/lib/device/dev-io.c.diff?r1=1.52&r2=1.53&cvsroot=lvm2&f=h There's one problem... we shouldn't use with a 2nd arg of 1... it should be -1. http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/tools/toollib.c.diff?r1=1.82&r2=1.83&cvsroot=lvm2&f=h And there's the other problem... dev_set(dev, UINT64_C(0), (size_t) 4096, value); will not clear out the whole device, just the first 4096 bytes of it (based on what dev_set does). untested patches applied upstream for those two problems lvm2-2.02.14-1 built fix verified in lvm2-2.02.14-1. marking this verified again. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0287.html |