LVM

The Logical Volume Manager or LVM is a volume manager used on Linux. It facilitates the management of storage volumes which are similar to disk partitions but with the added flexibility of:

• Resizing volumes
• Snapshotting volumes for consistent backups
• Span multiple disks together into a single large volume similar to JBOD.

Quick Usage

First, create a Volume Group (VG) that specifies which storage (the Physical Volumes, PV) to use. A VG will contain 4MB Physical Extents (PE) that are 'blocks' of storage that can be assigned to a Logical Volume (LV). PEs are mapped to Logical Extents (LE) inside LVs and are mapped by LVM with the mapping data saved in the VG's layout header. Since PEs are assigned, LVs can be resized by adding or removing PEs. However, the filesystem utilizing the volume must be shrunk first or expanded after the change using something like fs2resize.

To quickly get a filesystem up and running using LVM:

root@nsb:/# vgcreate ug_vg /dev/sdb
  Volume group "ug_vg " successfully created
  
  
root@nsb:/# vgdisplay ug_vg 
  --- Volume group ---
  VG Name               ug_vg 
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  1
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                0
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               836.62 GiB
  PE Size               4.00 MiB
  Total PE              214175
  Alloc PE / Size       0 / 0
  Free  PE / Size       214175 / 836.62 GiB
  VG UUID               WeggQU-zQf3-j3mk-OAFd-iUCQ-EDTo-ezxhcb

root@nsb:/# lvcreate -n ug -l 90%FREE ug_vg
  Logical volume "ug" created.

## After creating a LV, the available free PEs decrease as expected
root@nsc:~# vgdisplay ug_vg
...
  VG Size               836.62 GiB
  PE Size               4.00 MiB
  Total PE              214175
  Alloc PE / Size       192757 / 752.96 GiB
  Free  PE / Size       21418 / 83.66 GiB

# LVM volumes are placed under /dev with the VG name and LV name.
root@nsc:~# mkfs.ext4 /dev/ug_vg/ug

## If a VG needs to be renamed, use the vgrename command:
root@nsb:/# vgrename uga ug_vg

Recovering Volumes

Use vgscan to rescan for volume groups. This will create a file of the same name as the volume in /etc/lvm/backup/.

To restore a volume, use the vgcfgrestore command. For example, if there is a volume VolGroup01:

With the volume groups restored, use pvscan to look for physical volumes.

Activate the volume using vgchange VolGroup01 -a y

With the volume activated, look for logical volumes using lvscan. Logical volumes should show up in /dev/VolGroup01/LogVol00 for example and can be mounted.

In summary:

# vgscan                                  # Generates /etc/lvm/backup/VolGroup01
# cd /etc/lvm/backup
# vgcfgrestore -f VolGroup01 VolGroup01   # Restore VG using /etc/lvm/backup/VolGroup01
# vgscan                                  # verifies volume groups
# pvscan                                  # Looks for physical volumes
# vgchange VolGroup01 -a y                # Activates the volume group
# lvscan                                  # Looks for logical volumes
# mount /dev/VG01/LV00 /mnt/foo           # LVM volumes should be in /dev/vg/lv and should be mountable

See also:

• http://thecususergroup.proboards.com/thread/4156/recover-thecus-raid-pc

Mounting / Unmounting Volumes

If you have a LVM partition, you can see what physical volumes there are under the LVM by running:

# pvs
PV               VG                Fmt    Attr    PSize       PFree
/dev/hda2        VolGroup01        lvm2   a-      148.94G     32.00M

The volume group (VG) is VolumeGroup01. To view the logical volumes under this volume group, run:

# lvdisplay /dev/VolumeGroup01

Once you have located the logical volume you want to mount, say LogVol00, run:

# mount /dev/VolumeGroup01/LogVol00 /mnt/disk

Expanding Volume

If you expanded a disk that is using LVM (such as expanding the virtual disk of a virtual machine):

1. Expand the virtual disk
2. The OS might not be aware of the disk size change until a reboot. Reboot if the size is still incorrect.
3. Resize the partition that LVM is using using fdisk.
   1. Delete the partition
   2. Recreate the partition with the same starting location but with a larger size
   3. Run partprobe to update the partition size
4. Resize the LVM physical volume with pvresize /dev/sda1
5. pvscan should show the lvm having free space
6. Resize the LV. Eg: Add 1GB with lvresize -L +1G /dev/centos/root
7. Resize the filesystem.

An example from a virtual machine where the disk was expanded from 20GB to 40GB.

## Expand the partition <code>/dev/sda2</code> using <code>fdisk</code>. Then do the following.
[root@itsocaaspoc-bootstrap ~]# pvresize /dev/sda2
  Physical volume "/dev/sda2" changed
  1 physical volume(s) resized or updated / 0 physical volume(s) not resized
[root@itsocaaspoc-bootstrap ~]# pvscan
  PV /dev/sda2   VG centos          lvm2 [<39.00 GiB / 20.00 GiB free]
  Total: 1 [<39.00 GiB] / in use: 1 [<39.00 GiB] / in no VG: 0 [0   ]
[root@itsocaaspoc-bootstrap ~]# lvresize -L +1G /dev/centos/root
  Size of logical volume centos/root changed from <17.00 GiB (4351 extents) to <18.00 GiB (4607 extents).
  Logical volume centos/root successfully resized.
[root@itsocaaspoc-bootstrap ~]# lvs
  LV   VG     Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  root centos -wi-ao---- <18.00g
  swap centos -wi-ao----   2.00g
[root@itsocaaspoc-bootstrap ~]# xfs_growfs /
meta-data=/dev/mapper/centos-root isize=512    agcount=4, agsize=1113856 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0 spinodes=0
data     =                       bsize=4096   blocks=4455424, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 4455424 to 4717568
[root@itsocaaspoc-bootstrap ~]# xfs_info /
meta-data=/dev/mapper/centos-root isize=512    agcount=5, agsize=1113856 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0 spinodes=0
data     =                       bsize=4096   blocks=4717568, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

See Also

• Expanding XFS File System