- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RHEL 5 get "vg metadata too large for circular buf...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-29-2012 05:01 PM
02-29-2012 05:01 PM
RHEL 5 get "vg metadata too large for circular buffer" . Why ?
One of my teammate is getting this when trying to grow a volume an RHEL filesystem
Extending logical volume nms_u11 to 126.00 GB
VG datadg metadata too large for circular buffer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2012 12:42 AM
03-01-2012 12:42 AM
Re: RHEL 5 get "vg metadata too large for circular buffer" . Why ?
Hi,
By Default physical LVM volumes are created with 255 sectors of metadata space which is equivalent of 128KB.
If the data stored in the metadata exceeds the size allocated to it then you get that error, whenever you try to make a change that tries to modify the metadata.
use the below command to check the value of pvmetadatasize in /etc/lvm/lvm.conf
#grep pvmetadatasize /etc/lvm/lvm.conf
Check the backups for your volume group and see where the first physical extend begins. Using the default setting, it should begin at 384 PE's
#grep pestart /etc/lvm/backup/volgroup01
Physical LVM volumes need to be recreated with larger metadata size.
Physical volumes can be created with increased metadata size by using the below command:
#pvcreate --metadatasize 1020 /dev/mapper/newpvdisk
You can change the default metadata size in /etc/lvm/lvm.conf as shown below:
# Approximate default size of on-disk metadata areas in sectors.
# You should increase this if you have large volume groups or
# you want to retain a large on-disk history of your metadata changes.
# pvmetadatasize = 255
pvmetadatasize = 1020
After making the lvm.conf change, all pvcreate commands will use the new metadata size without requiring you to specify --metadatasize
Hope this helps.
Chhaya
I am an HP employee.
Was this post useful? - You may click the KUDOS! star to say thank you.