Description of problem: There's no easy way to tell how much (if any) metadata space is available on each PV. [root@taft-04 ~]# pvcreate /dev/sdb1 /dev/sdc1 /dev/sdd1 Physical volume "/dev/sdb1" successfully created Physical volume "/dev/sdc1" successfully created Physical volume "/dev/sdd1" successfully created [root@taft-04 ~]# pvcreate --metadatacopies 0 /dev/sdb2 /dev/sdc2 /dev/sdd2 Physical volume "/dev/sdb2" successfully created Physical volume "/dev/sdc2" successfully created Physical volume "/dev/sdd2" successfully created [root@taft-04 ~]# pvscan PV /dev/sdb1 lvm2 [136.23 GB] PV /dev/sdb2 lvm2 [136.23 GB] PV /dev/sdc1 lvm2 [136.23 GB] PV /dev/sdc2 lvm2 [136.23 GB] PV /dev/sdd1 lvm2 [930.89 GB] PV /dev/sdd2 lvm2 [930.89 GB] Total: 6 [2.35 TB] / in use: 0 [0 ] / in no VG: 6 [2.35 TB] [root@taft-04 ~]# pvs PV VG Fmt Attr PSize PFree /dev/sdb1 lvm2 -- 136.23G 136.23G /dev/sdb2 lvm2 -- 136.23G 136.23G /dev/sdc1 lvm2 -- 136.23G 136.23G /dev/sdc2 lvm2 -- 136.23G 136.23G /dev/sdd1 lvm2 -- 930.89G 930.89G /dev/sdd2 lvm2 -- 930.89G 930.89G Version-Release number of selected component (if applicable): [root@taft-04 ~]# rpm -q lvm2 lvm2-2.02.06-6.0.RHEL4
2.02.27 has "pvs -o +mda_count" *** This bug has been marked as a duplicate of 247444 ***
I read this one as slightly different to bug 247444 - it's asking about viewing how much space is remaining in the metadata areas, rather than how many MDAs exist and where they are. I guess that's easy enough to add to pvs etc. too though.
Ah, ok, so if mda_count is not enough, please reopen this.
As discussed on IRC this one's asking for the amount of free space left in the MDAs. Should be addressed along with the other metadata handling improvements.
Upstream commit: CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk 2007-11-05 17:17:56 Modified files: . : WHATS_NEW lib/format_text: format-text.c format-text.h layout.h text_label.c lib/metadata : metadata.c metadata.h lib/report : columns.h report.c Log message: Add pv_mda_free and vg_mda_free fields to reports for raw text format. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.728&r2=1.729 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/format_text/format-text.c.diff?cvsroot=lvm2&r1=1.84&r2=1.85 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/format_text/format-text.h.diff?cvsroot=lvm2&r1=1.22&r2=1.23 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/format_text/layout.h.diff?cvsroot=lvm2&r1=1.7&r2=1.8 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/format_text/text_label.c.diff?cvsroot=lvm2&r1=1.18&r2=1.19 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/metadata.c.diff?cvsroot=lvm2&r1=1.142&r2=1.143 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/metadata.h.diff?cvsroot=lvm2&r1=1.173&r2=1.174 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/report/columns.h.diff?cvsroot=lvm2&r1=1.23&r2=1.24 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/report/report.c.diff?cvsroot=lvm2&r1=1.63&r2=1.64
*** Bug 409071 has been marked as a duplicate of this bug. ***
So this one got in upstream? Let's set to POST then so we don't forget.
and mention *which* upstream version it got into: 2.02.29 from the WHATS_NEW diff above
Verified in lvm2-2.02.36-1.el4.
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-2008-0776.html