Difference between revisions of "LVM"

From ArchWiki
Jump to: navigation, search
(Add partition to a volume group)
(Configuration: link to root fs LVM snapshot article)
(40 intermediate revisions by 17 users not shown)
Line 2: Line 2:
 
[[Category:File systems]]
 
[[Category:File systems]]
 
[[cs:LVM]]
 
[[cs:LVM]]
 +
[[de:LVM]]
 
[[es:LVM]]
 
[[es:LVM]]
 
[[fr:LVM]]
 
[[fr:LVM]]
Line 15: Line 16:
 
{{Article summary wiki|Software RAID and LVM}}
 
{{Article summary wiki|Software RAID and LVM}}
 
{{Article summary wiki|System Encryption with LUKS}}
 
{{Article summary wiki|System Encryption with LUKS}}
 +
{{Article summary wiki|Encrypted LVM}}
 
{{Article summary end}}
 
{{Article summary end}}
  
 
==Introduction==
 
==Introduction==
 
{{Wikipedia|Logical Volume Manager (Linux)}}
 
{{Wikipedia|Logical Volume Manager (Linux)}}
 
+
===LVM Building Blocks===
[[LVM]] (Logical Volume Management) makes use of the [http://sources.redhat.com/dm/ device-mapper] feature of the Linux kernel to provide a system of partitions that is independent of the underlying disk's layout. With LVM you can abstract your storage space and have "virtual partitions" which makes it easier to extend and shrink partitions (subject to the filesystem you use allowing this) and add/remove partitions without worrying about whether you have enough contiguous space on a particular disk, without getting caught up in the problems of fdisking a disk that is in use (and wondering whether the kernel is using the old or new partition table) and without having to move other partition out of the way. This is strictly an ease-of-management issue: it does not provide any addition security. However, it sits nicely with the other two technologies we are using.
+
Logical Volume Management makes use of the [http://sources.redhat.com/dm/ device-mapper] feature of the Linux kernel to provide a system of partitions that is independent of the underlying disk's layout. With LVM you can abstract your storage space and have "virtual partitions" which makes it easier to extend and shrink partitions (subject to the filesystem you use allowing this) and add/remove partitions without worrying about whether you have enough contiguous space on a particular disk, without getting caught up in the problems of fdisking a disk that is in use (and wondering whether the kernel is using the old or new partition table) and without having to move other partition out of the way. This is strictly an ease-of-management issue: it does not provide any additional security. However, it sits nicely with the other two technologies we are using.
 
+
Note that LVM is not used for the boot partition, because of the bootloader problem.
+
{{Tip|/boot cannot reside in a LVM partition when using [[GRUB Legacy]], which does not support LVM. If you want /boot to reside in a LVM partition, use [[GRUB2]]. }}
+
  
 
The basic building blocks of LVM are:
 
The basic building blocks of LVM are:
Line 31: Line 30:
 
* '''Logical volume (LV)''': A "virtual/logical partition" that resides in a volume group and is composed of physical extents. Think of logical volumes as normal partitions.
 
* '''Logical volume (LV)''': A "virtual/logical partition" that resides in a volume group and is composed of physical extents. Think of logical volumes as normal partitions.
 
* '''Physical extent (PE)''': A small part of a disk (usually 4MB) that can be assigned to a logical Volume. Think of physical extents as parts of disks that can be allocated to any partition.
 
* '''Physical extent (PE)''': A small part of a disk (usually 4MB) that can be assigned to a logical Volume. Think of physical extents as parts of disks that can be allocated to any partition.
 
With LVM you can more easily handle your partitions (logical volumes) than normal hard drive partitions. For example, you can:
 
 
* Use ''any number'' of disks as one big disk(VG)
 
* Have partitions(LV) stretched ''over'' several disks (they can be as big as all of your disk storage together)
 
* Resize/create/delete partitions(LV) and disks(VG) ''as you like'' (it does not depend on position of the logical volumes within volume groups as with normal partitions)
 
* Resize/create/delete partitions(LV) and disks(VG) ''online'' (filesystems on them still need to be resized, but some support online resizing)
 
* ''Name'' your disks(VG) and partitions(LV) as you like
 
* Create small partitions(LV) and resize them "''dynamically''" as they get more filled (growing must be still done by hand, but you can do it online with some filesystems)
 
* ...
 
  
 
Example:  
 
Example:  
Line 65: Line 54:
 
     |_ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
 
     |_ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
  
To sum it all up: With LVM you can use all your storage space as one big disk (volume group) and have more flexibility over your partitions (logical volumes).
 
  
==Advantages==
+
===Advantages===
  
Here are some things you can do with LVM that you cannot (or cannot do easily) with just mdadm, MBR partitions, GPT partitions, parted/gparted and a file-level tool like rsync.
+
LVM gives you more flexibility than just using normal hard drive partitions:
# Online/live partition resizing
+
* Use any number of disks as one big disk.
# No need for an extended partition (not relevant for GPT)
+
* Have logical volumes stretched over several disks.
# Resize partitions regardless of their order on disk (no need to ensure surrounding available space)
+
* Create small logical volumes and resize them "dynamically" as they get more filled.
# Online/live migration of partitions being used by services without having to restart services
+
* Resize logical volumes regardless of their order on disk. It does not depend on the position of the LV within VG, there is no need to ensure surrounding available space.
 +
* Resize/create/delete logical and physical volumes online. Filesystems on them still need to be resized, but some support online resizing.
 +
* Online/live migration of LV being used by services to different disks without having to restart services.
 +
* Snapshots allow you to backup a frozen copy of the filesystem, while keeping service downtime to a minimum.
  
 
These can be very helpful in a server situation, desktop less so, but you must decide if the features are worth the abstraction.
 
These can be very helpful in a server situation, desktop less so, but you must decide if the features are worth the abstraction.
  
==Installation==
+
===Disadvantages===
Before doing anything we need to load the appropriate module:
+
# modprobe dm-mod
+
If you already have Arch Linux installed and you just want to add/try a partition with LVM, jump to [[Lvm#Partition_disks|partition disks]].
+
  
===Installing Arch Linux on LVM===
+
* Linux exclusive (almost). There is no official support in most other OS (FreeBSD, Windows..).
Prior to running Arch Linux install scripts (/arch/setup) to install Arch Linux, you need to partition your disk with {{Ic|cfdisk}} (or any other tool of your liking). Because grub legacy (grub with version less than 1.0) cannot boot from LVM logical volumes you cannot have {{ic|/boot}} in LVM, so you need to create a boot partition. 100MB should be enough. The other solution would be to use lilo or grub with version 1.95 or newer.
+
* Additional steps in setting up the system, more complicated.
 +
* If you use the [[btrfs]] filesystem, its Subvolume feature will also give you the benefit of having a flexible layout. In that case, using the additional Abstraction layer of LVM may be unnecessary.
  
===Partition disks===
+
==Installing Arch Linux on LVM==
Next you need to create a partition for LVM. Its filesystem type should be 'Linux LVM', so use a partition id 0x8e (filesystem type: 8e). You need to create only one LVM partition on each disk you want to use with LVM. Your logical volumes will reside inside these partitions so size them accordingly. If you will use only LVM and no other external partitions, use all the free space on each disk.
+
You should create your LVM Volumes between the [[Partitioning]] and [[File_Systems#Step_2:_create_the_new_file_system|mkfs]] steps of the Installation Procedure. Instead of directly formating a partition to be you root file file-system, it will be created inside a logical volume (LV).  
  
{{Warning|/boot cannot reside in LVM when using [[GRUB Legacy]], which does not support LVM. If you want /boot to reside in a LVM partition, use [[GRUB2]]. }}
+
Quick overview:
 +
* Create partition(s) where your PV will reside. Set the partition type to 'Linux LVM', which is 8e if you use MBR, 8e00 for GPT.
 +
* Create your physical volumes (PV). If you have one disk it is best to just create one PV in one large partition. If you have multiple disks you can create partitions on each of them and create a PV on each partition.
 +
* Create your volume group (VG) and add all the PV to it.
 +
* Create logical volumes (LV) inside your VG.
 +
* Continue with “Format the partitions” step of Beginners Guide.
 +
* When you reach the “Create initial ramdisk environment” step in the Beginners Guide, add the lvm hook to mkinitcpio.conf (see below for details).
  
{{Tip|All LVM partitions on all disks can be configured to appear as one big disk.}}
+
{{Warning|/boot cannot reside in LVM when using [[GRUB Legacy]], which does not support LVM. [[GRUB]] users do not have this limitation. If you need to use GRUB Legacy, you must create a separate /boot partition and format it directly. }}
  
 
===Create physical volumes===
 
===Create physical volumes===
Now you need to initialize these partitions so they can be used by LVM. Use {{Ic|fdisk -l}} to find out which partitions have filesystem type 'Linux LVM' and create a physical volume on them:
+
Make sure you target the right partitions! To find the partitions with type 'Linux LVM':
  # pvcreate /dev/sda2
+
* MBR system: {{Ic|fdisk -l}}
Substitute {{ic|/dev/sda2}} with all your partitions to create physical volumes on all of them. This command creates a header on each partition so it can be used for LVM.
+
* GPT system: {{Ic|lsblk}} and then {{Ic|gdisk -l <disk-device>}}
 +
 
 +
Create a physical volume on them:
 +
  # pvcreate <disk-device> (e.g.: pvcreate /dev/sda2)
 +
This command creates a header on each partition so it can be used for LVM.
 
You can track created physical volumes with:
 
You can track created physical volumes with:
 
  # pvdisplay
 
  # pvdisplay
Line 134: Line 133:
 
  # vgscan
 
  # vgscan
 
  # vgchange -ay
 
  # vgchange -ay
Now you can create filesystems on logical volumes and mount them as normal partitions (if you are installing Arch linux, skip this step. Use the arch installer to pick the LVM partitions that you have created):
+
Now you can create filesystems on logical volumes and mount them as normal partitions (if you are installing Arch linux, refer to [[Beginners' Guide#Mount the partitions|mounting the partitions]] for additional details):
  # mkfs.ext3 /dev/mapper/VolGroup00-lvolhome
+
  # mkfs.ext4 /dev/mapper/VolGroup00-lvolhome
 
  # mount /dev/mapper/VolGroup00-lvolhome /home
 
  # mount /dev/mapper/VolGroup00-lvolhome /home
If you are installing Arch linux, start /arch/setup, go to ''Prepare Hard Drive'' directly to step 3 ''Set Filesystem Mountpoints'' and '''''read the [[Lvm#Important|Important]] section below before proceeding with installation!'''''
 
  
=== Set filesystem mountpoints ===
+
{{Warning|When choosing mountpoints, just select your newly created logical volumes (use: {{ic|/dev/mapper/Volgroup00-lvolhome}}). Do NOT select the actual partitions on which logical volumes were created (do not use: {{ic|/dev/sda2}}).}}
* When choosing mountpoints, just select your newly created logical volumes (use: {{ic|/dev/mapper/Volgroup00-lvolhome}}).<br>Do NOT select the actual partitions on which logical volumes were created (do not use: {{ic|/dev/sda2}}).
+
  
=== Configure system ===
+
=== Add lvm hook to mkinitcpio.conf ===
  
For late-boot activation (non-root-filesystem) of volume groups, enable the {{ic|lvm}} unit file,
+
You'll need to make sure the {{Ic|udev}} and {{Ic|lvm2}} [[mkinitcpio]] hooks are enabled.
  
{{bc|# systemctl enable lvm.service}}
+
{{Ic|udev}} is there by default. Edit the file and insert {{Ic|lvm2}} between {{Ic|block}} and {{Ic|filesystem}} like so:
  
Or, if you still use sysvinit, modify {{ic|USELVM}} appropriately:
+
{{hc|/etc/mkinitcpio.conf:|<nowiki>HOOKS="base udev ... block lvm2 filesystems"</nowiki>}}
  
{{hc|# vim /etc/rc.conf|<nowiki>USELVM="yes"</nowiki>}}
+
Afterwards, you can continue in normal installation instructions with the  [[Mkinitcpio#Image_creation_and_activation|create an initial ramdisk]] step.
  
For early-boot activation (if the volume group that you're interested in does contain your root filesystem), you'll need to enable the {{ic|lvm2}} [[mkinitcpio]] hook.
+
== Configuration ==
 +
=== Advanced options ===
 +
If you need monitoring (needed for snapshots) you can enable lvmetad.
 +
For this set {{ic|1=use_lvmetad = 1}} in {{ic|/etc/lvm/lvm.conf}}.
 +
This is the default by now.  
  
{{hc|# vim /etc/mkinitcpio.conf|<nowiki>HOOKS="... lvm2 filesystems"</nowiki>}}
+
You can restrict the volumes that are activated automatically by setting the {{Ic|auto_activation_volume_list}} in {{Ic|/etc/lvm/lvm.conf}}. If in doubt, leave this option commented out.
  
Afterwards, [[Mkinitcpio#Image_creation_and_activation|rebuild]] the initramfs.
 
 
== Configuration ==
 
 
=== Grow logical volume ===
 
=== Grow logical volume ===
 
To grow a logical volume you first need to grow the logical volume and then the filesystem to use the newly created free space. Let us say we have a logical volume of 15GB with ext3 on it and we want to grow it to 20G. We need to do the following steps:  
 
To grow a logical volume you first need to grow the logical volume and then the filesystem to use the newly created free space. Let us say we have a logical volume of 15GB with ext3 on it and we want to grow it to 20G. We need to do the following steps:  
Line 210: Line 208:
 
You can verify the removal of your logical volume by typing "lvs" as root again (see first step of this section).
 
You can verify the removal of your logical volume by typing "lvs" as root again (see first step of this section).
  
=== Add partition to a volume group ===
+
=== Add physical volume to a volume group ===
  
{{Accuracy|}}
+
You first create a new physical volume on the block device you wish to use, then extend your volume group
  
To add a partition to your volume group you must first make its type 'Linux LVM' (for example with {{Ic|cfdisk}}). Then you need to create a physical volume on it and extend the volume group over it:
+
{{bc|1=
# pvcreate /dev/sdb1
+
# pvcreate /dev/sdb1
# vgextend VolGroup00 /dev/sdb1
+
# vgextend VolGroup00 /dev/sdb1}}
Now you have free space in your volume group that can be used by logical volumes in this group.
+
 
 +
This of course will increase the total number of physical extents on your volume group, which can be allocated by logical volumes as you see fit.
  
{{Tip|You can add partitions from any disks to volume groups.}}
+
{{Note|It is considered good form to a partition table on your storage medium below LVM, and use the appropriate type code: {{ic|8e}} for MBR, and {{ic|8e00}} for GPT partitions.}}
  
 
=== Remove partition from a volume group ===
 
=== Remove partition from a volume group ===
Line 250: Line 249:
  
 
snapshots are primarily used to provide a frozen copy of a filesystem to make backups; a backup taking two hours provides a more consistent image of the filesystem than directly backing up the partition.
 
snapshots are primarily used to provide a frozen copy of a filesystem to make backups; a backup taking two hours provides a more consistent image of the filesystem than directly backing up the partition.
 +
 +
See [[Create root filesystem snapshots with LVM]] for automating the creation of clean root filesystem snapshots during system startup
 +
for backup and rollback.
 +
 +
[[Encrypted_LVM]]
  
 
== Troubleshooting ==
 
== Troubleshooting ==
 +
===Changes that could be required due to changes in the Arch-Linux defaults===
 +
The {{ic|1=use_lvmetad = 1}} must be set in {{ic|/etc/lvm/lvm.conf}}. This is the default now - if you have a {{ic|lvm.conf.pacnew}} file, you must merge this change.
 +
 
===LVM commands do not work===
 
===LVM commands do not work===
 
*Load proper module:
 
*Load proper module:
 
  # modprobe dm_mod
 
  # modprobe dm_mod
 +
 +
The {{ic|dm_mod}} module should be automatically loaded. In case it does not, you can try:
 +
 +
{{hc|/etc/mkinitcpio.conf:|<nowiki>MODULES="dm_mod ..."</nowiki>}}
 +
 +
You will need to [[Mkinitcpio#Image_creation_and_activation|rebuild]] the initramfs to commit any changes you made.
 +
 +
 
*Try preceding commands with ''lvm'' like this:
 
*Try preceding commands with ''lvm'' like this:
 
  # lvm pvdisplay
 
  # lvm pvdisplay
  
=== Set filesystem mountpoints page does not show logical volumes ===
+
=== Logical Volumes do not show up ===
If you are installing on a system where there is an existing volume group, you may find that even after doing "modprobe dm-mod" you do not see the list of logical volumes.
+
If you are trying to mount existing logical volumes, but they do not show up in {{ic|lvscan}}, you can use the following commands to activate them:
  
In this case, you may also need to do:
 
 
  # vgscan
 
  # vgscan
or:
+
  # vgchange -ay
  # vgchange -ay <volgroup>
+
 
+
in order to activate the volume group and make the logical volumes available.
+
  
 
===LVM on removable media===
 
===LVM on removable media===
Line 288: Line 299:
 
  # vgscan
 
  # vgscan
 
  # vgchange -ay <volume group name>
 
  # vgchange -ay <volume group name>
 +
 +
===kernel options===
 +
In kernel options, you may need {{ic|dolvm}}. {{ic|<nowiki>root=</nowiki>}} should be set to the logical volume, e.g {{ic|<nowiki>/dev/mapper/{vg-name}-{lv-name}</nowiki>}}
 +
 +
 +
===obsolete stuff===
 +
If you still use sysvinit, modify {{ic|USELVM}} appropriately:
 +
 +
{{hc|/etc/rc.conf:|<nowiki>USELVM="yes"</nowiki>}}
 +
  
 
== Additional resources ==
 
== Additional resources ==

Revision as of 17:50, 27 April 2013

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

Introduction

Template:Wikipedia

LVM Building Blocks

Logical Volume Management makes use of the device-mapper feature of the Linux kernel to provide a system of partitions that is independent of the underlying disk's layout. With LVM you can abstract your storage space and have "virtual partitions" which makes it easier to extend and shrink partitions (subject to the filesystem you use allowing this) and add/remove partitions without worrying about whether you have enough contiguous space on a particular disk, without getting caught up in the problems of fdisking a disk that is in use (and wondering whether the kernel is using the old or new partition table) and without having to move other partition out of the way. This is strictly an ease-of-management issue: it does not provide any additional security. However, it sits nicely with the other two technologies we are using.

The basic building blocks of LVM are:

  • Physical volume (PV): Partition on hard disk (or even hard disk itself or loopback file) on which you can have volume groups. It has a special header and is divided into physical extents. Think of physical volumes as big building blocks which can be used to build your hard drive.
  • Volume group (VG): Group of physical volumes that are used as storage volume (as one disk). They contain logical volumes. Think of volume groups as hard drives.
  • Logical volume (LV): A "virtual/logical partition" that resides in a volume group and is composed of physical extents. Think of logical volumes as normal partitions.
  • Physical extent (PE): A small part of a disk (usually 4MB) that can be assigned to a logical Volume. Think of physical extents as parts of disks that can be allocated to any partition.

Example:

Physical disks
                
  Disk1 (/dev/sda):
     _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
    |Partition1 50GB (Physical volume) |Partition2 80GB (Physical volume)     |
    |/dev/sda1                         |/dev/sda2                             |
    |_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
                                  
  Disk2 (/dev/sdb):
     _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
    |Partition1 120GB (Physical volume)                 |
    |/dev/sdb1                                          |
    | _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __ _ _|
LVM logical volumes

  Volume Group1 (/dev/MyStorage/ = /dev/sda1 + /dev/sda2 + /dev/sdb1):
     _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
    |Logical volume1 15GB  |Logical volume2 35GB      |Logical volume3 200GB               |
    |/dev/MyStorage/rootvol|/dev/MyStorage/homevol    |/dev/MyStorage/mediavol             |
    |_ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ _ _ |_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |


Advantages

LVM gives you more flexibility than just using normal hard drive partitions:

  • Use any number of disks as one big disk.
  • Have logical volumes stretched over several disks.
  • Create small logical volumes and resize them "dynamically" as they get more filled.
  • Resize logical volumes regardless of their order on disk. It does not depend on the position of the LV within VG, there is no need to ensure surrounding available space.
  • Resize/create/delete logical and physical volumes online. Filesystems on them still need to be resized, but some support online resizing.
  • Online/live migration of LV being used by services to different disks without having to restart services.
  • Snapshots allow you to backup a frozen copy of the filesystem, while keeping service downtime to a minimum.

These can be very helpful in a server situation, desktop less so, but you must decide if the features are worth the abstraction.

Disadvantages

  • Linux exclusive (almost). There is no official support in most other OS (FreeBSD, Windows..).
  • Additional steps in setting up the system, more complicated.
  • If you use the btrfs filesystem, its Subvolume feature will also give you the benefit of having a flexible layout. In that case, using the additional Abstraction layer of LVM may be unnecessary.

Installing Arch Linux on LVM

You should create your LVM Volumes between the Partitioning and mkfs steps of the Installation Procedure. Instead of directly formating a partition to be you root file file-system, it will be created inside a logical volume (LV).

Quick overview:

  • Create partition(s) where your PV will reside. Set the partition type to 'Linux LVM', which is 8e if you use MBR, 8e00 for GPT.
  • Create your physical volumes (PV). If you have one disk it is best to just create one PV in one large partition. If you have multiple disks you can create partitions on each of them and create a PV on each partition.
  • Create your volume group (VG) and add all the PV to it.
  • Create logical volumes (LV) inside your VG.
  • Continue with “Format the partitions” step of Beginners Guide.
  • When you reach the “Create initial ramdisk environment” step in the Beginners Guide, add the lvm hook to mkinitcpio.conf (see below for details).
Warning: /boot cannot reside in LVM when using GRUB Legacy, which does not support LVM. GRUB users do not have this limitation. If you need to use GRUB Legacy, you must create a separate /boot partition and format it directly.

Create physical volumes

Make sure you target the right partitions! To find the partitions with type 'Linux LVM':

  • MBR system: fdisk -l
  • GPT system: lsblk and then gdisk -l <disk-device>

Create a physical volume on them:

# pvcreate <disk-device> (e.g.: pvcreate /dev/sda2)

This command creates a header on each partition so it can be used for LVM. You can track created physical volumes with:

# pvdisplay
Note: If using a SSD use pvcreate --dataalignment 1m /dev/sda2 (for erase block size < 1MiB), see e.g. here

Create volume group

Next step is to create a volume group on this physical volume. First you need to create a volume group on one of the new partitions and then add to it all other physical volumes you want to have in it:

# vgcreate VolGroup00 /dev/sda2
# vgextend VolGroup00 /dev/sdb1

Also you can use any other name you like instead of VolGroup00 for a volume group when creating it. You can track how your volume group grows with:

# vgdisplay
Note: You can create more than one volume group if you need to, but then you will not have all your storage presented as one disk.

Create logical volumes

Now we need to create logical volumes on this volume group. You create a logical volume with the next command by giving the name of a new logical volume, its size, and the volume group it will live on:

# lvcreate -L 10G VolGroup00 -n lvolhome

This will create a logical volume that you can access later with /dev/mapper/Volgroup00-lvolhome or /dev/VolGroup00/lvolhome. Same as with the volume groups, you can use any name you want for your logical volume when creating it.

To create swap on a logical volume, an additional argument is needed:

# lvcreate -C y -L 10G VolGroup00 -n lvolswap

The -C y is used to create a contiguous partition, which means that your swap space does not get partitioned over one or more disks nor over non-contiguous physical extents.

If you want to fill all the free space left on a volume group, use the next command:

# lvcreate -l +100%FREE VolGroup00 -n lvolmedia

You can track created logical volumes with:

# lvdisplay
Note: You may need to load the device-mapper kernel module (modprobe dm-mod) for the above commands to succeed:
Tip: You can start out with relatively small logical volumes and expand them later if needed. For simplicity, leave some free space in the volume group so there is room for expansion.

Create filesystems and mount logical volumes

Your logical volumes should now be located in /dev/mapper/ and /dev/YourVolumeGroupName. If you cannot find them, use the next commands to bring up the module for creating device nodes and to make volume groups available:

# modprobe dm-mod
# vgscan
# vgchange -ay

Now you can create filesystems on logical volumes and mount them as normal partitions (if you are installing Arch linux, refer to mounting the partitions for additional details):

# mkfs.ext4 /dev/mapper/VolGroup00-lvolhome
# mount /dev/mapper/VolGroup00-lvolhome /home
Warning: When choosing mountpoints, just select your newly created logical volumes (use: /dev/mapper/Volgroup00-lvolhome). Do NOT select the actual partitions on which logical volumes were created (do not use: /dev/sda2).

Add lvm hook to mkinitcpio.conf

You'll need to make sure the udev and lvm2 mkinitcpio hooks are enabled.

udev is there by default. Edit the file and insert lvm2 between block and filesystem like so:

/etc/mkinitcpio.conf:
HOOKS="base udev ... block lvm2 filesystems"

Afterwards, you can continue in normal installation instructions with the create an initial ramdisk step.

Configuration

Advanced options

If you need monitoring (needed for snapshots) you can enable lvmetad. For this set use_lvmetad = 1 in /etc/lvm/lvm.conf. This is the default by now.

You can restrict the volumes that are activated automatically by setting the auto_activation_volume_list in /etc/lvm/lvm.conf. If in doubt, leave this option commented out.

Grow logical volume

To grow a logical volume you first need to grow the logical volume and then the filesystem to use the newly created free space. Let us say we have a logical volume of 15GB with ext3 on it and we want to grow it to 20G. We need to do the following steps:

# lvextend -L 20G VolGroup00/lvolhome (or lvresize -L +5G VolGroup00/lvolhome)
# resize2fs /dev/VolGroup00/lvolhome

You may use lvresize instead of lvextend.

If you want to fill all the free space on a volume group, use the next command:

# lvextend -l +100%FREE VolGroup00/lvolhome
Warning: Not all filesystems support growing without loss of data and/or growing online.
Note: If you do not resize your filesystem, you will still have a volume with the same size as before (volume will be bigger but partly unused).

Shrink logical volume

Because your filesystem is probably as big as the logical volume it resides on, you need to shrink the filesystem first and then shrink the logical volume. Depending on your filesystem, you may need to unmount it first. Let us say we have a logical volume of 15GB with ext3 on it and we want to shrink it to 10G. We need to do the following steps:

# resize2fs /dev/VolGroup00/lvolhome 9G
# lvreduce -L 10G VolGroup00/lvolhome (or lvresize -L -5G VolGroup00/lvolhome)
# resize2fs /dev/VolGroup00/lvolhome

Here we shrunk the filesystem more than needed so that when we shrunk the logical volume we did not accidentally cut off the end of the filesystem. After that we normally grow the filesystem to fill all free space left on logical volume. You may use lvresize instead of lvreduce.

Warning:
  • Do not reduce the filesystem size to less than the amount of space occupied by data or you risk data loss.
  • Not all filesystems support shrinking without loss of data and/or shrinking online.
Note: It is better to reduce the filesystem to a smaller size than the logical volume, so that after resizing the logical volume, we do not accidentally cut off some data from the end of the filesystem.

Remove logical volume

Warning: Before you remove a logical volume, make sure to move all data that you want to keep somewhere else, otherwise it will be lost!

First, find out the name of the logical volume you want to remove. You can get a list of all logical volumes installed on the system with:

# lvs

Next, look up the mountpoint for your chosen logical volume...:

$ df -h

... and unmount it:

# umount /your_mountpoint

Finally, remove the logical volume:

# lvremove /dev/yourVG/yourLV

Confirm by typing Template:Keypress and you are done.

Do not forget, to update /etc/fstab!

You can verify the removal of your logical volume by typing "lvs" as root again (see first step of this section).

Add physical volume to a volume group

You first create a new physical volume on the block device you wish to use, then extend your volume group

# pvcreate /dev/sdb1
# vgextend VolGroup00 /dev/sdb1

This of course will increase the total number of physical extents on your volume group, which can be allocated by logical volumes as you see fit.

Note: It is considered good form to a partition table on your storage medium below LVM, and use the appropriate type code: 8e for MBR, and 8e00 for GPT partitions.

Remove partition from a volume group

All of the data on that partition needs to be moved to another partition. Fortunately, LVM makes this easy:

# pvmove /dev/sdb1

If you want to have the data on a specific physical volume, specify that as the second argument to pvmove:

# pvmove /dev/sdb1 /dev/sdf1

Then the physical volume needs to be removed from the volume group:

# vgreduce myVg /dev/sdb1

Or remove all empty physical volumes:

# vgreduce --all vg0

And lastly, if you want to use the partition for something else, and want to avoid LVM thinking that the partition is a physical volume:

# pvremove /dev/sdb1

Snapshots

Introduction

LVM allows you to take a snapshot of your system in a much more efficient way than a traditional backup. It does this efficiently by using a COW (copy-on-write) policy. The initial snapshot you take simply contains hard-links to the inodes of your actual data. So long as your data remains unchanged, the snapshot merely contains its inode pointers and not the data itself. Whenever you modify a file or directory that the snapshot points to, LVM automatically clones the data, the old copy referenced by the snapshot, and the new copy referenced by your active system. Thus, you can snapshot a system with 35GB of data using just 2GB of free space so long as you modify less than 2GB (on both the original and snapshot).

Configuration

You create snapshot logical volumes just like normal ones.

# lvcreate --size 100M --snapshot --name snap01 /dev/mapper/vg0-pv

With that volume, you may modify less than 100M of data, before the snapshot volume fills up.

It is important to have the dm-snapshot module listed in the MODULES variable of /etc/mkinitcpio.conf, otherwise the system will not boot. If you do this on an already installed system, make sure to rebuild the image with

# mkinitcpio -g /boot/initramfs-linux.img

Todo: scripts to automate snapshots of root before updates, to rollback... updating menu.lst to boot snapshots (separate article?)

snapshots are primarily used to provide a frozen copy of a filesystem to make backups; a backup taking two hours provides a more consistent image of the filesystem than directly backing up the partition.

See Create root filesystem snapshots with LVM for automating the creation of clean root filesystem snapshots during system startup for backup and rollback.

Encrypted_LVM

Troubleshooting

Changes that could be required due to changes in the Arch-Linux defaults

The use_lvmetad = 1 must be set in /etc/lvm/lvm.conf. This is the default now - if you have a lvm.conf.pacnew file, you must merge this change.

LVM commands do not work

  • Load proper module:
# modprobe dm_mod

The dm_mod module should be automatically loaded. In case it does not, you can try:

/etc/mkinitcpio.conf:
MODULES="dm_mod ..."

You will need to rebuild the initramfs to commit any changes you made.


  • Try preceding commands with lvm like this:
# lvm pvdisplay

Logical Volumes do not show up

If you are trying to mount existing logical volumes, but they do not show up in lvscan, you can use the following commands to activate them:

# vgscan
# vgchange -ay

LVM on removable media

Symptoms:

~$ sudo vgscan
 Reading all physical volumes.  This may take a while...
 /dev/backupdrive1/backup: read failed after 0 of 4096 at 319836585984: Input/output error
 /dev/backupdrive1/backup: read failed after 0 of 4096 at 319836643328: Input/output error
 /dev/backupdrive1/backup: read failed after 0 of 4096 at 0: Input/output error
 /dev/backupdrive1/backup: read failed after 0 of 4096 at 4096: Input/output error
 Found volume group "backupdrive1" using metadata type lvm2
 Found volume group "networkdrive" using metadata type lvm2

Cause:

Removing an external LVM drive without deactivating the volume group(s) first. Before you disconnect, make sure to:
# vgchange -an <volume group name>

Fix: (assuming you already tried to activate the volume group with vgchange -ay <vg>, and are receiving the Input/output errors

# vgchange -an <volume group name>
Unplug the external drive and wait a few minutes
# vgscan
# vgchange -ay <volume group name>

kernel options

In kernel options, you may need dolvm. root= should be set to the logical volume, e.g /dev/mapper/{vg-name}-{lv-name}


obsolete stuff

If you still use sysvinit, modify USELVM appropriately:

/etc/rc.conf:
USELVM="yes"


Additional resources