linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
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: Wed, 24 Nov 2010 21:35:38 +0000 (UTC)	[thread overview]
Message-ID: <ick0fa$tm$2@taco.int.tagonline.com> (raw)
In-Reply-To: icjsgr$tm$1@taco.int.tagonline.com

On Wed, 24 Nov 2010 20:28:11 +0000, Andrew Gideon wrote:

> But even if two segments are moved from dislocated locations to
> immediately adjacent locations, I see nothing which says that these two
> segments would be combined into a single segment.  So I'm not clear how
> fragmentation can be reduced.

This one part I was able to answer myself with some experimentation.  
pvmove is actually smart enough that, if two segments that are logically 
contiguous are placed such that they're physically contiguous, they are 
aggregated into a single segment.

Unfortunately, I cannot use pvmove in my production environment since it 
needs to create a temporary volume for a move and this runs into the 
"metadata too large" error.

So I'm still looking at how to solve this problem either with new PVs 
(and removing the metadata from the previous PVs, if I've understood this 
correctly) and/or moving the metadata to an external file.

	- Andrew

  reply	other threads:[~2010-11-24 21: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 [this message]
2010-11-24 23:02 ` Ray Morris
2010-11-25  3:35   ` Andrew Gideon
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='ick0fa$tm$2@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 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).