From: Andrew Gideon <ag2827189@tagmall.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvremove or vgextend: metadata too large for circular buffer
Date: Sat, 12 Mar 2011 03:48:36 +0000 (UTC) [thread overview]
Message-ID: <ileqek$nji$4@taco.int.tagonline.com> (raw)
In-Reply-To: 20110311170154.0475f82e@bettercgi.com
On Fri, 11 Mar 2011 17:01:54 -0600, Ray Morris wrote:
> What I did was to allocate MUCH more space on the new PVs,
> make a new VG from them, then copy LVs from one of the old PVs. Then
> recreate that PV with more metadata space, add it to the new VG, etc.
> until all of the PVs are in the new VG, with far more metadata space.
Creating a new VG is my worst-case scenario, but that will be expensive
in terms of time - time during which I cannot do expansion of volumes.
It's a little frustrating.
How risky is the idea of editing a backup file and doing the restore? If
I screw it up, I can always do a re-restore of the proper data, no?
Thanks...
Andrew
prev parent reply other threads:[~2011-03-12 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 20:05 [linux-lvm] lvremove or vgextend: metadata too large for circular buffer Andrew Gideon
2011-03-11 22:31 ` Andrew Gideon
2011-03-11 23:01 ` Ray Morris
2011-03-12 3:48 ` Andrew Gideon [this message]
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='ileqek$nji$4@taco.int.tagonline.com' \
--to=ag2827189@tagmall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.