4/25/2019 4.3.

Volume Group Administration

C U S T O M E R (https://access.redhat.com/)
P O R TA L


 4.3. Volume Group Administration

This section describes the commands that perform the various aspects of volume gro

4.3.1. Creating Volume Groups
 To create a volume group from one or more physical volumes, use the vgcreate com
command creates a new volume group by name and adds at least one physical volum

The following command creates a volume group named vg1 that contains physical vo
nage /dev/sde1.

vgcreate vg1 /dev/sdd1 /dev/sde1

wnloa

When physical volumes are used to create a volume group, its disk space is divided
This extent is the minimum amount by which the logical volume may be increased or
tain numbers of extents will have no impact on I/O performance of the logical volume.

You can specify the extent size with the -s option to the vgcreate command if the def
suitable. You can put limits on the number of physical or logical volumes the volume g
port -p and -l arguments of the vgcreate command.

By default, a volume group allocates physical extents according to common-sense ru

 parallel stripes on the same physical volume. This is the normal allocation policy. You
argument of the vgcreate command to specify an allocation policy of contiguous, any

 The contiguous policy requires that new extents are adjacent to existing extents. If th
extents to satisfy an allocation request but a normal allocation policy would not use th
policy will, even if that reduces performance by placing two stripes on the same phys
policy places new extents on the same physical volume as existing extents in the sam
volume. These policies can be changed using the vgchange command.

In general, allocation policies other than normal are required only in special cases wh
We use cookies on our websites to deliver our online services. Details about how we use cookies and


unusual or nonstandard extent allocation.

how you may disable them are set out in our Privacy Statement
(//www.redhat.com/en/about/privacy-policy#cookies). By using this website you agree to our use
of cookies. LVM volume groups and underlying logical volumes are included in the device specia 
/dev directory with the following layout:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/Cluster_Logical_Volume_Manager/VG_admin.html 1/2
4/25/2019 4.3. Volume Group Administration

C U S T O M E R (https://access.redhat.com/)
/dev/vg/lv/
P O R TA L


For example, if you create two volume groups myvg1 and myvg2, each with three logic
 lvo2, and lvo3, this create six device special files:

 /dev/myvg1/lv01 /dev/myvg1/lv02 /dev/myvg1/lv03 /dev/myvg2/lv01 /dev/myvg2

 The maximum device size with LVM is 8 Exabytes on 64-bit CPUs.

nage
All systems operational (https://status.redhat.com)

Privacy Statement
wnloa (http://www.redhat.com/en/about/privacy-policy)

Customer Portal Terms of Use

(https://access.redhat.com/help/terms/)

tain All Policies and Guidelines

(http://www.redhat.com/en/about/all-policies-
guidelines)
Copyright © 2019 Red Hat, Inc.

port

We use cookies on our websites to deliver our online services. Details about how we use cookies and


how you may disable them are set out in our Privacy Statement
(//www.redhat.com/en/about/privacy-policy#cookies). By using this website you agree to our use
of cookies. 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/Cluster_Logical_Volume_Manager/VG_admin.html 2/2