Set up a 64-bit Linux instance (a Bronze-level offering) with the Linux Logical Volume Manager (LVM).
Capture a private image and provision it as a new Platinum instance.
Grow the LVM volume and file system to accommodate the new physical volumes.
Configure LVM across physical volumes using Linux LVM-type partitions.
Background on LVM and the test scenario
First, a description of LVM concepts and the test scenario for those who may not be familiar with LVM.
Note: You are about to configure Linux LVM: Here be Dragons. Mind the gap.
The Linux LVM is organized into physical volumes (PVs), volume groups (VGs), and logical volumes (LVs)
- Physical volume: Physical HDDs, physical HDD partitions (such as /dev/vdb1).
- Extents: PVs are split into chunks called PEs (physical extents). Logical extents (LEs) map 1:1 to PEs and are used for the physical-to-logical volume mapping.
- Volume group: A virtual disk consisting of aggregated physical volumes. VGs can be logically partitioned into LVs.
- Logical volume: Acts as a virtual disk partition. After creating a VG you can create LVs in that VG. They can be used as raw block devices, swap devices, or for creating a (mountable) file system just like disk partitions.
- File system: LVs can be used as raw devices or swap, but are more commonly "formatted" with a supported file system and mounted to defined mountpoint. I'll format the LV as an ext3 file system in this scenario.
- Partition table: You'll use tools like fdisk, sfdisk, or cfdisk to manipulate the block device partition table and create Linux LVM (8e) type partitions.
- Read More>