Bug 455453
| Summary: | RHEL5 cmirror tracker: small mirror creation fails | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | cmirror | Assignee: | Jonathan Earl Brassow <jbrassow> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.3 | CC: | agk, ccaulfie, dwysocha, edamato, heinzm, mbroz |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-20 21:25:20 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
2008-07-15 15:57:46 UTC
*** Bug 454337 has been marked as a duplicate of this bug. *** Non mirrors still work with small sizes: [root@hayes-02 ~]# lvcreate -n linear -L 5M hayes Rounding up size to full physical extent 8.00 MB Logical volume "linear" created Looks like the bug exists between 30M - 40M: [root@hayes-02 ~]# lvcreate -m 1 -n mirror1 -L 100M hayes Logical volume "mirror1" created [root@hayes-02 ~]# lvcreate -m 1 -n mirror2 -L 90M hayes Rounding up size to full physical extent 92.00 MB Logical volume "mirror2" created [root@hayes-02 ~]# lvcreate -m 1 -n mirror3 -L 80M hayes Logical volume "mirror3" created [root@hayes-02 ~]# lvcreate -m 1 -n mirror4 -L 70M hayes Rounding up size to full physical extent 72.00 MB Logical volume "mirror4" created [root@hayes-02 ~]# lvcreate -m 1 -n mirror5 -L 60M hayes Logical volume "mirror5" created [root@hayes-02 ~]# lvcreate -m 1 -n mirror6 -L 50M hayes Rounding up size to full physical extent 52.00 MB Logical volume "mirror6" created [root@hayes-02 ~]# lvcreate -m 1 -n mirror7 -L 40M hayes Logical volume "mirror7" created [root@hayes-02 ~]# lvcreate -m 1 -n mirror8 -L 30M hayes Rounding up size to full physical extent 32.00 MB [ FAIL ] Here are the failure messages: Jul 15 11:12:02 bp-xen-03 clogd[2176]: [1ir9GXk6] Checkpoint prepared for 2 Jul 15 11:12:02 bp-xen-03 clogd[2176]: [1ir9GXk6] Checkpoint data available for node 2 Jul 15 11:12:02 bp-xen-03 clogd[2176]: Sending checkpointed data to 2 Jul 15 11:12:02 bp-xen-03 clogd[2176]: [1ir9GXk6] Failed to open checkpoint for 2: Reason = 7 Jul 15 11:12:02 bp-xen-03 clogd[2176]: Failed to export checkpoint 'Reason = 7' stands for 'SA_AIS_ERR_INVALID_PARAM'... So, I will need to check with steve dake to figure out the proper ranges for the parameters... everything should be the same, except the size of the sections. The magic number seems to be either 39M or 40M. 40M worked in the example above, but not here: [root@hayes-02 ~]# lvcreate -m 1 -n mirrorA -L 50M hayes Rounding up size to full physical extent 52.00 MB Logical volume "mirrorA" created [root@hayes-02 ~]# lvcreate -m 1 -n mirrorB -L 41M hayes Rounding up size to full physical extent 44.00 MB Logical volume "mirrorB" created [root@hayes-02 ~]# lvcreate -m 1 -n mirrorC -L 40M hayes Error locking on node hayes-03: Command timed out Error locking on node hayes-02: Command timed out Error locking on node hayes-01: Command timed out Aborting. Failed to activate new LV to wipe the start of it. commit 6c8d7408095782bb00b5361a7df5973f3dcda183
Author: Jonathan Brassow <jbrassow>
Date: Tue Jul 15 11:58:26 2008 -0500
clogd: Fix for bug 455453: small mirror creation fails
Was setting the checkpoint attribute 'attr.maxSectionSize'
with the size of the bitmap. However, when mirrors are
really small (<= 30M) other sections may have a larger
size and need to considered.
Fix verified in cmirror-1.1.20-1.el5/kmod-cmirror-0.1.11-2.el5. 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 therefore 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/RHEA-2009-0158.html |