From: Andrew Gideon <ag2827189@tagmall.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Solving the "metadata too large for circular buffer" condition
Date: Thu, 25 Nov 2010 03:35:37 +0000 (UTC) [thread overview]
Message-ID: <ickli9$tm$4@taco.int.tagonline.com> (raw)
In-Reply-To: 1290639756.1076.20@raydesk1.bettercgi.com
On Wed, 24 Nov 2010 17:02:36 -0600, Ray Morris wrote:
> If you have two redundant PVs or free space, one could move LVs in
> order to empty an older PV, then recreate it with larger metadata.
> pvmove can be used to move active LVs, or dd is much faster for inactive
> ones.
I don't have much free space on the storage device. To get this would
take a fair bit of time in that I'd need to add new drives and
incorporate them into the RAID set.
But I do have *some* space thanks to "rounding errors" (or "fudge
factor"). It's not enough to move much data around, but I could build a
couple of small PVs for use primarily as metadata repositories.
Does this make sense?
In the long term, as I do add new disks, I can create new "real" PVs with
the larger metadata segments, increasing the redundancy. Ultimately, I
can get ahead of the game and start pvmove-ing segments off the PVs on
which I'd have disabled the metadata because the space allocated is too
small.
But, in the short term, I'm looking to see how I can most quickly return
this device to "full service" (being able to extend or add volumes). And
that seems to be using a pair of tiny PVs as metadata-only. If that
makes sense.
Does it?
Thanks...
Andrew
next prev parent reply other threads:[~2010-11-25 3:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 20:28 [linux-lvm] Solving the "metadata too large for circular buffer" condition Andrew Gideon
2010-11-24 21:35 ` Andrew Gideon
2010-11-24 23:02 ` Ray Morris
2010-11-25 3:35 ` Andrew Gideon [this message]
2010-11-24 23:07 ` Ray Morris
2010-11-25 3:28 ` [linux-lvm] Unable to use metadata.dirs in lvm.conf? (Was: Re: Solving the "metadata too large for circular buffer" condition) Andrew Gideon
2010-11-26 16:03 ` Peter Rajnoha
2010-11-29 14:50 ` Andrew Gideon
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='ickli9$tm$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.