Bug 720883
Summary: | Disk with an existing LVM physical volume on it only gets an LVM metadata size of 1M when creating a storage domain | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Mark Huth <mhuth> |
Component: | vdsm22 | Assignee: | Dan Kenigsberg <dkenigsb> |
Status: | CLOSED ERRATA | QA Contact: | yeylon <yeylon> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 5.8 | CC: | abaron, bazulay, byount, cpelland, danken, dpaikov, ewarszaw, iheim, kgrainge, mkalinin, mkenneth, plyons, srevivo, ykaul |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | storage | ||
Fixed In Version: | vdsm-4.5-65.el5 | Doc Type: | Bug Fix |
Doc Text: |
If a disk already had an LVM physical volume defined on it and you defined a storage domain on the disk, Red Hat Enterprise Linux would create an LVM metadata area on the disk of only 1M instead of 100M because of an error in the code. The error has been fixed and now Red Hat Enterprise Linux creates LVM metadata areas that are always 100M in size by default.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-21 04:52:53 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: | |||
Bug Blocks: | 729322 |
Description
Mark Huth
2011-07-13 05:23:39 UTC
I guess it was plain carelessness of commit c3fa5e7ce1e2f4d249a20c803894d2d7b6413db7 (for bug 514283 - increase the vg metadata size). and should be fixed by: http://gerrit.usersys.redhat.com/710 Author: Dan Kenigsberg <danken> Date: Thu Jul 14 21:32:57 2011 +0300 BZ#720883 re-create pv with reasonable metadatasize No need to have a different metadata size for bare luns and recreated pvs. Change-Id: I820765e86e17d3222e42702fef452830949a6e0d would the recent customer issues have been averted if we had this patch? Running 'vgs -o vg_name,vg_tags,vg_mda_size,vg_mda_free' on a hypervisor will show if any of the storage domains are susceptible (like e0bb0e61-b274-473f-9392-e741629c2489 here): [root@h2 ~]# vgs -o vg_name,vg_tags,vg_mda_size,vg_mda_free VG VG Tags VMdaSize VMdaFree 563c53f3-9c11-4852-922e-9350cf5bbdd4 RHAT_storage_domain 100.06M 50.02M HostVG 188.00K 91.00K e0bb0e61-b274-473f-9392-e741629c2489 RHAT_storage_domain 1.06M 538.50K To test patch of comment 1, create storage domains out of raw LUNs and out of pre-existing PVs. In all cases, metadata size as reported by vgs -o vg_name,vg_tags,vg_mda_size,vg_mda_free should be 100M (and never 1M). Checked on 4.5-65. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: If a disk already had an LVM physical volume defined on it and you defined a storage doman on the disk, Red Hat Enterprise Linux would create an LVM metadata area on the disk of only 1M instead of 100M because of an error in the code. The error has been fixed and now Red Hat Enterprise Linux creates LVM metadata areas that are always 100M in size by default. Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -If a disk already had an LVM physical volume defined on it and you defined a storage doman on the disk, Red Hat Enterprise Linux would create an LVM metadata area on the disk of only 1M instead of 100M because of an error in the code. The error has been fixed and now Red Hat Enterprise Linux creates LVM metadata areas that are always 100M in size by default.+If a disk already had an LVM physical volume defined on it and you defined a storage domain on the disk, Red Hat Enterprise Linux would create an LVM metadata area on the disk of only 1M instead of 100M because of an error in the code. The error has been fixed and now Red Hat Enterprise Linux creates LVM metadata areas that are always 100M in size by default. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0169.html |