From: kanonmatswe <kanonmatswe@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] shrink VG and PV
Date: Tue, 18 May 2010 07:29:18 +0200 [thread overview]
Message-ID: <4BF225AE.3080303@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005171721260.2347@bmsred.bmsi.com>
On 05/17/2010 11:30 PM, Stuart D. Gathman wrote:
>Conclusion: always use only one metadata area per PV (but on multiple PVs
>when available).
I don't know how that second metadata area got there :) I don't think I'm using it or will have any use for it.
So there is no way of erasing it? If I do "backup VG, redo pvcreate with uuid& restorefile, restore VG"
as Alasdair said as quoted by malahal@us.ibm.com, I will erase all data, right? The solution seems to be
roughly equivalent to backing up all data and then repartition before copying back?
next prev parent reply other threads:[~2010-05-18 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 19:44 [linux-lvm] shrink VG and PV Dael Elcar
2010-05-17 20:56 ` Malahal Naineni
2010-05-17 21:14 ` Malahal Naineni
2010-05-17 21:30 ` Stuart D. Gathman
2010-05-18 5:29 ` kanonmatswe [this message]
2010-05-18 9:13 ` Bryn M. Reeves
2010-05-18 9:38 ` Bryn M. Reeves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF225AE.3080303@gmail.com \
--to=kanonmatswe@gmail.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).