All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Eheman <eheman@funsoft.com>
To: Linux-lvm <linux-lvm@redhat.com>
Subject: [linux-lvm] error msg: VG vgc1 metadata too large for circular buffer
Date: Fri, 27 Jan 2006 15:35:41 -0500	[thread overview]
Message-ID: <43DA841D.3080208@funsoft.com> (raw)

I am running SuSE 9.3 PRO.
# uname -r
2.6.11.4-21.9-bigsmp

I pulled the latest CVS tree two days ago for both device-mapper and 
LVM2 because I hit a problem with the level of those that came with SuSE 
9.3.  I need to be able to create hundreds (say 400 or 500) logical 
volumes with the application I am working with.

The new CVS code allowed me to get many many more than I was able to get 
prior to going with the new code from the CVS trees.

I created a volume group on a 500+G drive with -M2, omitted 
metadatasize, and let the allocation size default to 4M (probably dumb 
given the size of the volumes I am creating).

I managed to about 392 volumes created in the volume group. Now any 
attempt to create additional or to delete a logical volume from that 
group fails with a message:
"VG vgc1 metadata too large for circular buffer"

# lvremove -vvvvv vgc1/33901_vgc1_392
<lots-of-stuff-snipped>

#metadata/pv_manip.c:241         /dev/sdc1 381:  89154    234: 
33901_vgc1_382(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 382:  89388    234: 
33901_vgc1_383(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 383:  89622    234: 
33901_vgc1_384(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 384:  89856    234: 
33901_vgc1_385(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 385:  90090    234: 
33901_vgc1_386(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 386:  90324    234: 
33901_vgc1_387(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 387:  90558    234: 
33901_vgc1_388(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 388:  90792    234: 
33901_vgc1_389(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 389:  91026    234: 
33901_vgc1_390(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 390:  91260    234: 
33901_vgc1_391(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 391:  91494    234: NULL(0:0)
#metadata/pv_manip.c:241         /dev/sdc1 392:  91728  47815: NULL(0:0)
#format_text/export.c:121         Doubling metadata output buffer to 131072
#format_text/format-text.c:408   VG vgc1 metadata too large for circular 
buffer
#metadata/metadata.c:782         <backtrace>
#locking/file_locking.c:59       Unlocking /var/lock/lvm/V_vgc1
#device/dev-io.c:483         Closed /dev/sdc1
x260:/usr/flexes


I can destroy the data. In fact, that is what I would like to do, but 
softly using lvremove, vgremove, pvremove if possible. But I can't get 
around the current error.

Advice,please?  Are there parameters I can give during the creation of 
the group or volume to avoid this?
-- 
Gary Eheman
Fundamental Software, Inc.
http://www.funsoft.com

             reply	other threads:[~2006-01-27 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27 20:35 Gary Eheman [this message]
2006-01-27 21:33 ` [linux-lvm] error msg: VG vgc1 metadata too large for circular buffer Alasdair G Kergon
2006-01-27 22:21   ` Gary Eheman

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=43DA841D.3080208@funsoft.com \
    --to=eheman@funsoft.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.