Bug 490004
Summary: | Creation of mirrored logical volume with VG extent-size of 1K fails | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Nate Straz <nstraz> |
Component: | lvm2 | Assignee: | Milan Broz <mbroz> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.8 | CC: | agk, cmarthal, dwysocha, edamato, heinzm, jbrassow, mbroz, prockai, pvrabec |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 477040 | Environment: | |
Last Closed: | 2009-05-18 20:10:46 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: | |||
Bug Depends On: | 477040 | ||
Bug Blocks: | 490021 |
Description
Nate Straz
2009-03-12 20:25:44 UTC
There are two parts, one is kernel part, which fixes log device constructor to check properly for log size and prevents "access beyond end of device". Second is lvm2 part, which correctly calculates disk log size here. Please clone that bug for kernel (I think that kernel part is more important here, should be easy patch). I'll check how complicated is the lvm2 usespace part to backport... Fixed in lvm2-2.02.42-5.el4 Fix verified in lvm2-2.02.42-5.el4. SCENARIO - [create_mirror_on_1Kextent_vg] Create a mirror on a VG with an extent size of only 1K Recreating PVs/VG with smaller (1K) extent size hayes-01: vgcreate -s 1K mirror_sanity /dev/etherd/e1.1p1 /dev/etherd/e1.1p2 /dev/etherd/e1.1p3 /dev/etherd/e1.1p4 /dev/etherd/e1.1p5 hayes-01: lvcreate -m 1 -n mirror_on_1Kextent_vg -L 20M mirror_sanity Deactivating mirror mirror_on_1Kextent_vg... and removing Restoring VG to default extent size 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/RHBA-2009-0967.html |