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] lvremove or vgextend: metadata too large for circular buffer
Date: Fri, 11 Mar 2011 22:31:29 +0000 (UTC)	[thread overview]
Message-ID: <ile7s1$nji$3@taco.int.tagonline.com> (raw)
In-Reply-To: ildv9o$nji$2@taco.int.tagonline.com

On Fri, 11 Mar 2011 20:05:12 +0000, Andrew Gideon wrote:

> 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.

I've tried vgcfgrestore, but this too yields:

	metadata too large for circular buffer

I ran some commands with -vvv.  The output which seems to always 
immediately precede the error is:

	Doubling metadata output buffer to 131072

I also noticed that it appears to be looking at /dev/sdi and /dev/sdj.  
These are two PVs I'd tried to add, but where vgextend also issued the 
"too large..." error.  These two PVs do not appear in 'vgdisplay -v'.

[root@backup2 backup]# /usr/sbin/lvremove -d -vvv -f /dev/jetarray004/i2-backup0 2>&1  | egrep 'sd[ij]' 
        Opened /dev/sdi RW O_DIRECT
        /dev/sdi: block size is 4096 bytes
      /dev/sdi: lvm2 label detected
        lvmcache: /dev/sdi: now in VG #orphans_lvm2 (#orphans_lvm2)
        Closed /dev/sdi
        Opened /dev/sdj RW O_DIRECT
        /dev/sdj: block size is 4096 bytes
      /dev/sdj: lvm2 label detected
        lvmcache: /dev/sdj: now in VG #orphans_lvm2 (#orphans_lvm2)
        Closed /dev/sdj
[root@backup2 backup]# 

Is there perhaps some "internal" VG (ie. #orphans_lvm2) that I'd be
able to successfully remove?

Thanks...

	Andrew

  reply	other threads:[~2011-03-11 22:31 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 [this message]
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='ile7s1$nji$3@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).