From: Andrew Gideon <ag2827189@tagmall.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvremove or vgextend: metadata too large for circular buffer
Date: Fri, 11 Mar 2011 20:05:12 +0000 (UTC) [thread overview]
Message-ID: <ildv9o$nji$2@taco.int.tagonline.com> (raw)
We're hitting the "metadata too large for circular buffer" problem. Last
time this occurred, I was able to clear out a little space by removing
some unused volumes, and then make more space by selective use of pvmove
to defragment. This worked well.
However, that time I didn't get the error from lvremove. This time, that
is occurring. So I don't seem to be able to make any space.
Once I execute lvremove on a volume, the "LV Status" becomes "NOT
available". The command 'lvdisplay -m' still shows the segments, however.
How can I resolve this? Trashing the entire VG is not something I can
afford.
I created new PVs with larger allocations of space for metadata, but I
cannot even add these to the VG. The vgextend command also fails with
"metadata too large for circular buffer".
- Andrew
next reply other threads:[~2011-03-11 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 20:05 Andrew Gideon [this message]
2011-03-11 22:31 ` [linux-lvm] lvremove or vgextend: metadata too large for circular buffer Andrew Gideon
2011-03-11 23:01 ` Ray Morris
2011-03-12 3:48 ` 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='ildv9o$nji$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).