[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] lvremove or vgextend: metadata too large for circular buffer



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

You may be able to manually do your removes on the output of 
vgcfgbackup, then use vgcfgrestore.  Be careful.

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

   What I did was to allocate MUCH more space on the new PVs, 
make a new VG from them, then copy LVs from one of the old PVs.
Then recreate that PV with more metadata space, add it to the 
new VG, etc. until all of the PVs are in the new VG, with far 
more metadata space.
-- 
Ray Morris
support bettercgi com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php




On Fri, 11 Mar 2011 20:05:12 +0000 (UTC)
Andrew Gideon <ag2827189 tagmall com> wrote:

> 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
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm redhat com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]