Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We ran into a problem when a set of PVs were added without using the appropriate metadata size. Consequently, we cannot add and remove volumes, create or remove snaps, run vgreduce and pvmoreve or any almost any other LVM command without getting this message:

Metadata too large for circular buffer

In my research, it came down to this:

  • Restore from backup configuration
  • Create a new volume group and migrating the LVMs.

I am not enthused about the first option, but the second option is almost worse because we have about over 10 terabytes of data to move.

What other alternatives we can try? Note that we did attempt to use the file-based metadata option, but for some reason, lvm is ignoring that.

Platform: CentOS 5.7

share|improve this question
up vote 2 down vote accepted

We ended up having to do the following:

  • Run vgcfgbackup.
  • Edited the backup and remove the PVs
  • run vgcfgrestore.

It worked. YMMV, of course, if you try this fix.

(Of note is that editing the VG configuration backup is not generally recommended)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.