Sponsored Content
Full Discussion: LVM extent size
Operating Systems Linux LVM extent size Post 302469236 by zaxxon on Friday 5th of November 2010 05:38:48 AM
Old 11-05-2010
From the man page of vgcreate:
Code:
       -s, --physicalextentsize PhysicalExtentSize[kKmMgGtT]
              Sets  the  physical  extent size on physical volumes of this volume group.  A size suffix (k for kilobytes up to t
              for terabytes) is optional, megabytes is the default if no suffix is present.  The default is 4 MB and it must  be
              at least 1 KB and a power of 2.

              Once this value has been set, it is difficult to change it without recreating the volume group which would involve
              backing up and restoring data on any logical volumes.  However, if no extents need moving for  the  new  value  to
              apply, it can be altered using vgchange -s.
...

It can not even only be different on distributions but even for Volume Groups on the same machine, if people used different values.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Size of LVM header in non bootable disk

hi, i have a query regarding the size of the LVM header. Since the LVM header of a bootable disk is always 2912KB. The header size of a non bootable disk is not fixed. In Bootable disk after the LVM header (2912 KB=5824 sectors)the user data starts or we can say LV extents starts. If i extend any... (0 Replies)
Discussion started by: gorayen
0 Replies

2. Solaris

command to find out total size of a specific file size (spread over the server)

hi all, in my server there are some specific application files which are spread through out the server... these are spread in folders..sub-folders..chid folders... please help me, how can i find the total size of these specific files in the server... (3 Replies)
Discussion started by: abhinov
3 Replies

3. HP-UX

file system full (1 block extent)

When i run dmesg, I get the following message which clearly indicates that the file system is full. Please let me know what does (1 block extent) means in the following error message? msgcnt 1 vxfs : mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent) Thanks (6 Replies)
Discussion started by: Adams Nave
6 Replies

4. HP-UX

How to reduce LVM to create another LVM

Hi, I'm new to HP-UX. I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3 Thanks (4 Replies)
Discussion started by: lamoul
4 Replies

5. Shell Programming and Scripting

The scripts not able to make the file to size 0, every times it go back to its original size

#!/bin/sh ########################################################################################################## #This script is being used for AOK application for cleaning up the .out files and zip it under logs directory. # IBM # Created #For pdocap201/pdoca202 .out files for AOK #1.... (0 Replies)
Discussion started by: mridul10_crj
0 Replies

6. Shell Programming and Scripting

Script to read file size and send email only if size > 0.

Hi Experts, I have a script like $ORACLE_HOME/bin/sqlplus username/password # << ENDSQL set pagesize 0 trim on feedback off verify off echo off newp none timing off set serveroutput on set heading off spool Schemaerrtmp.txt select ' TIMESTAMP COMPUTER NAME ... (5 Replies)
Discussion started by: welldone
5 Replies

7. Solaris

Block-based allocation and Extent-based allocation in Solaris

Hi guys! Could you tell me what's this figure about? (See the attached figure below.) This is a representation of block allocation filesystem and extent allocation filesystem in Solaris. Does this mean that in a block-based allocation, data are placed in individual blocks while in... (0 Replies)
Discussion started by: arah
0 Replies

8. UNIX for Dummies Questions & Answers

How to convert non LVM root partition to LVM?

Hi Guys, I m using redhat 6, I have installed root partition as non-LVM . Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies

9. UNIX for Advanced & Expert Users

Physical disk IO size smaller than fragment block filesystem size ?

Hello, in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies

10. Red Hat

How to reduce the LVM Size in RHEL/Centos 7 ?

Hi All, I have one logical volume with size as 900G and it is mounted as xfs file system. Now I want to reduce this partition to 500G. So I followed the below steps. unmount the mount point /home Reduced the volume using the command Now I remounted the partition. But the problem... (3 Replies)
Discussion started by: kalpeer
3 Replies
VGCREATE(8)						      System Manager's Manual						       VGCREATE(8)

NAME
vgcreate - create a volume group SYNOPSIS
vgcreate [--addtag Tag] [--alloc AllocationPolicy] [-A|--autobackup {y|n}] [-c|--clustered {y|n}] [-d|--debug] [-h|--help] [-l|--maxlogi- calvolumes MaxLogicalVolumes] [-M|--metadatatypetype] [-p|--maxphysicalvolumes MaxPhysicalVolumes] [--[vg]metadatacopies] NumberOf- Copies|unmanaged|all] [-s|--physicalextentsize PhysicalExtentSize[bBsSkKmMgGtTpPeE]] [-t|--test] [-v|--verbose] [--version] [ PHYSICAL DEVICE OPTIONS ] VolumeGroupName PhysicalDevicePath [PhysicalDevicePath...] DESCRIPTION
vgcreate creates a new volume group called VolumeGroupName using the block special device PhysicalDevicePath. If PhysicalDevicePath was not previously configured for LVM with pvcreate (8), the device will be initialized with the same default values used with pvcreate. If non-default pvcreate values are desired, they may be given on the commandline with the same options as pvcreate. See PHYSICAL DEVICE OPTIONS for available options. Note that the restore-related options such as --restorefile, --uuid, and --physicalvol- umesize are not available. If a restore operation is needed, use pvcreate (8) and vgcfgrestore (8). OPTIONS
See lvm for common options. -c, --clustered {y|n} If clustered locking is enabled, this defaults to y indicating that this Volume Group is shared with other nodes in the cluster. If the new Volume Group contains only local disks that are not visible on the other nodes, you must specify --clustered n. If the cluster infrastructure is unavailable on a particular node at a particular time, you may still be able to use such Volume Groups. -l, --maxlogicalvolumes MaxLogicalVolumes Sets the maximum number of logical volumes allowed in this volume group. The setting can be changed with vgchange. For volume groups with metadata in lvm1 format, the limit and default value is 255. If the metadata uses lvm2 format, the default value is 0 which removes this restriction: there is then no limit. -p, --maxphysicalvolumes MaxPhysicalVolumes Sets the maximum number of physical volumes that can belong to this volume group. The setting can be changed with vgchange. For volume groups with metadata in lvm1 format, the limit and default value is 255. If the metadata uses lvm2 format, the value 0 removes this restriction: there is then no limit. If you have a large number of physical volumes in a volume group with metadata in lvm2 format, for tool performance reasons, you should consider some use of --pvmetadatacopies 0 as described in pvcreate(8), and/or use --vgmetadatacopies. --vgmetadatacopies NumberOfCopies|unmanaged|all Sets the desired number of metadata copies in the volume group. If set to a non-zero value, LVM will automatically manage the 'metadataignore' flags on the physical volumes (see pvcreate or pvchange --metadataignore) in order to achieve NumberOfCopies copies of metadata. If set to unmanaged, LVM will not automatically manage the 'metadataignore' flags. If set to all, LVM will first clear all of the 'metadataignore' flags on all metadata areas in the volume group, then set the value to unmanaged. The vgmetadata- copies option is useful for volume groups containing large numbers of physical volumes with metadata as it may be used to minimize metadata read and write overhead. The default value is unmanaged. -s, --physicalextentsize PhysicalExtentSize[bBsSkKmMgGtTpPeE] Sets the physical extent size on physical volumes of this volume group. A size suffix (k for kilobytes up to t for terabytes) is optional, megabytes is the default if no suffix is present. The default is 4 MB and it must be at least 1 KB and a power of 2. Once this value has been set, it is difficult to change it without recreating the volume group which would involve backing up and restoring data on any logical volumes. However, if no extents need moving for the new value to apply, it can be altered using vgchange -s. If the volume group metadata uses lvm1 format, extents can vary in size from 8KB to 16GB and there is a limit of 65534 extents in each logical volume. The default of 4 MB leads to a maximum logical volume size of around 256GB. If the volume group metadata uses lvm2 format those restrictions do not apply, but having a large number of extents will slow down the tools but have no impact on I/O performance to the logical volume. The smallest PE is 1KB. The 2.4 kernel has a limitation of 2TB per block device. PHYSICAL DEVICE OPTIONS
The following options are available for initializing physical devices in the volume group. These options are further described in the pvcreate man page. -f, --force -y, --yes -Z, --zero y|n --labelsector sector --metadatasize size --pvmetadatacopies copies --dataalignment alignment --dataalignmentoffset alignment_offset EXAMPLES
To create a volume group named test_vg using physical volumes /dev/sdk1, and /dev/sdl1 with default physical extent size of 4MB: vgcreate test_vg /dev/sdk1 /dev/sdl1 SEE ALSO
lvm(8), pvdisplay(8), pvcreate(8), vgdisplay(8), vgextend(8), vgreduce(8), lvcreate(8), lvdisplay(8), lvextend(8), lvreduce(8) Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) VGCREATE(8)
All times are GMT -4. The time now is 10:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy