LVM commands return "metadata too large for circular buffer": metadata area exhausted

Solution Verified - Updated -

Issue

  • I'm having problem on pvmove and other LVM commands with one of our server. LVM commands performed thta change the Volume Group configuration results in error messages:
# pvmove -v -i 10 /dev/sdco1:86535-86791 
   Finding volume group "VolGroup01" 
  Detected pvmove in progress for /dev/sdco1 
    Found volume group "VolGroup01" 
    Found volume group "VolGroup01" 
    Checking progress every 10 seconds 
  /dev/sdco1: Moved: 100.0% 
  VG VolGroup01 metadata too large 
  ABORTING: Failed to write new data locations to disk. 
  • I'v tried to abort pvmove operation:

    # pvmove --abort 
      VG <volume-group-name> metadata too large for circular buffer 
      ABORTING: Failed to write new data locations to disk.
    
  • Running commands such as vgreduce, vgextend, lvcreate, lvremove or any other command that modifies metadata will return the following error:

    VG <volume-group-name> metadata too large for circular buffer 
    ABORTING: Failed to write new data locations to disk.
    

Environment

  • Red Hat Enterprise Linux 4 - 9
  • LVM2 configuration with a large combination of following in a LVM Volume Group (VG):
    • many LVM Physical Volumes (PV)
    • many LVM Logical volumes (LV)
    • many incremental LV growth changes

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content