What Does Physical volume Mean?
On This Page
What do you want to do?
Quick Definition
A physical volume is a hard drive or partition that has been prepared to work with a volume manager. This preparation lets the operating system combine multiple physical volumes into larger, more flexible storage units. It is the basic building block for technologies like LVM on Linux or disk management on Windows.
Common Commands & Configuration
pvcreate /dev/sdc1Initializes the partition /dev/sdc1 as an LVM physical volume, writing metadata and assigning a UUID.
Tests the first step in LVM setup. Candidates must ensure the device is not already in use and has no filesystem.
pvdisplay /dev/sdbDisplays detailed attributes of the physical volume /dev/sdb, including its UUID, size, and volume group membership.
A tool for verifying PV state and allocation. Exams ask for the command to show all PV details.
pvmove /dev/sdd1 /dev/sde1Moves all physical extents from /dev/sdd1 to /dev/sde1 within the same volume group, enabling safe removal of the source PV.
Common in disk replacement scenarios. Tests understanding of online data migration.
pvchange -a n /dev/sdf1Deactivates the physical volume /dev/sdf1, preventing it from being used by LVM while preserving its data.
Knowledge of deactivating PVs for maintenance or replacement is frequently tested.
pvremove /dev/sdg1Removes LVM metadata from /dev/sdg1, making it a raw device again. Requires the PV to not be part of a volume group.
Used to decommission a PV. Exams check that the PV must first be removed from its VG before using this command.
pvs --noheadings -o pv_name,pv_uuid,vg_name -S pv_used=0Lists all unused physical volumes (not allocated to any volume group) along with their UUIDs.
Advanced filtering with 'pvs' is a key skill for efficient system management and scripting in certifications.
Physical volume appears directly in 31exam-style practice questions in Courseiva's question bank — one of the most-tested concepts on CompTIA A+ Core 1. Practise them →
Must Know for Exams
Physical volumes are a core topic in several IT certification exams, especially those focusing on Linux system administration, storage management, and virtualization. For the Red Hat Certified Engineer (RHCE) and Red Hat Certified System Administrator (RHCSA) exams, knowledge of LVM is tested thoroughly. Candidates must know how to create physical volumes using pvcreate, display their properties with pvs and pvdisplay, and remove them with pvremove. Objectives often include creating a volume group from multiple physical volumes, extending a logical volume when a physical volume is full, and moving physical extents off a failing disk. These tasks require a solid understanding of the relationship between PVs, VGs, and LVs.
For the Linux Professional Institute (LPIC-1 and LPIC-2) exams, physical volumes appear under objectives related to disk partitioning and filesystems. The LPIC-2 exam specifically includes advanced storage management, where candidates must be able to manage LVM snapshots, resize logical volumes, and handle physical volume migration. Similarly, the CompTIA Linux+ exam covers LVM concepts, including the role of physical volumes in volume groups. Although not as deep as RHCE, the exam expects you to know the commands and the purpose of each component.
In the storage domain, exams like Dell EMC Proven Professional or NetApp NCDA may reference physical volumes in the context of RAID groups or aggregate storage. While these exams use proprietary terminology, the underlying concept of initializing a block device for use in a storage pool is identical. Even Microsoft exams for Windows Server (e.g., AZ-800 or 70-740) deal with Storage Spaces, where a physical disk becomes a physical volume when added to a storage pool. Understanding the concept helps you grasp how storage pools work across different platforms.
In exams, physical volumes are typically tested through scenario-based questions. You might be asked to identify the correct order of operations when adding a new hard drive to an existing LVM setup: first create a partition, then create the physical volume, then extend the volume group, and finally extend the logical volume. Another common question asks which command to use to check the size and free space on a physical volume, with pvdisplay or pvs being the correct answer. Expect multiple-choice, fill-in-the-blank, and simulation questions where you must execute the correct commands in a virtual environment. A deep understanding of physical volumes will help you answer these questions correctly and quickly.
Simple Meaning
Think of a physical volume as a single piece of land, like a plot or a field. Before you can build anything useful on that land, you need to survey it, mark its boundaries, and register it with the local planning office. In the same way, a physical volume is a raw storage device, such as a hard drive or a partition, that has been initialized so that a volume manager knows it exists and can use it. The volume manager then groups these plots together into larger estates, called volume groups, which can be subdivided into logical volumes, the actual spaces where you store files.
Imagine you have two hard drives in your computer, each one a separate plot of land. On their own, you could use one for your documents and the other for your photos. But if you want a single large space to hold everything, you would need to join them. With physical volumes, you initialize both drives, add them to a volume group, and then create one big logical volume that spans both drives. The operating system sees this logical volume as one continuous drive, even though it is actually spread across two physical devices. This gives you the freedom to resize, move, or snapshot your storage without having to physically rearrange your hardware.
Physical volumes are the lowest level of abstraction in storage management. They deal with raw blocks and sectors, not with files or folders. When you create a physical volume, the volume manager writes a small amount of metadata to the device, marking it as ready for use. This metadata contains information about which volume group the physical volume belongs to and how the data is organized. Without physical volumes, you would be stuck with the fixed partitioning of traditional disk management, where changing the size of a partition often means deleting it and starting over.
Full Technical Definition
A physical volume (PV) is a fundamental concept in logical volume management (LVM) systems, such as LVM2 on Linux, ZFS pools on Solaris and FreeBSD, or Windows Storage Spaces. It represents a block device, typically a hard disk, a solid-state drive, or a disk partition, that has been initialized by the volume manager with a specific metadata format. This initialization process writes a label to the device, usually at the very beginning (e.g., the first 4 KiB of the disk in LVM2), which identifies the device as a physical volume and records details like the volume group it belongs to, its physical extents, and the size of those extents. The metadata is stored in a format that the volume manager can read and update, allowing dynamic changes to storage allocation.
In LVM2, which is the most common implementation on Linux, physical volumes are created using the pvcreate command. This command writes an LVM label to the specified device, which includes a UUID (Universally Unique Identifier) for the PV, the size and layout of physical extents (PEs), and a pointer to the volume group metadata area. Physical extents are fixed-size chunks, typically 4 MiB by default, that act as the smallest allocatable unit. When a physical volume is added to a volume group (VG), the PV contributes its PEs to the pool. Logical volumes (LVs) are then created by allocating PEs from the VG. The LV’s data is striped or concatenated across the underlying PVs at the extent level, providing performance and redundancy options.
The technical implementation involves several components: the device mapper subsystem in the Linux kernel, the LVM userspace tools (pvcreate, vgcreate, lvcreate, etc.), and the metadata stored on the PV itself. Physical volumes can be whole disks, partitions, or even software RAID arrays. They support operations like pvmove, which relocates physical extents from one PV to another without taking the logical volume offline, enabling online storage migration. Physical volumes also interact with filesystems: the filesystem sits on top of a logical volume, which is built from the PEs of one or more physical volumes. From the filesystem’s perspective, the logical volume appears as a contiguous block device, hiding the underlying complexity of multiple physical devices. Key performance considerations include the placement of metadata, the size of physical extents, and the alignment of the PV on the underlying disk geometry to avoid performance penalties.
Real-Life Example
Imagine you are organizing a community garden. You have several unfenced plots of land scattered around a neighborhood. Each plot on its own is small and irregularly shaped. To create a large, usable garden, you first need to register each plot with the community garden association. This registration process is like creating a physical volume: you are telling the association that this plot exists, has boundaries, and is available for use. The association records the plot’s dimensions and assigns it a unique ID. Now the plot is a physical volume, ready to be pooled with others.
Next, you combine several neighboring plots into one large garden area. You knock down the fences between them, mark a new perimeter, and call this combined area a volume group. The individual plots are still there underground, but above ground, you see one continuous garden. You then divide this large garden into beds using low borders. Each bed is a logical volume. One bed you reserve for tomatoes, another for carrots. The gardeners (the operating system) see each bed as a separate space. They do not care that the tomato bed might be partly on plot A and partly on plot B.
If a neighbor wants to move away and take back their plot (their physical volume), you can use a tool like pvmove to carefully transplant all the plants from that plot to another plot within the same garden, without disturbing the beds. This is exactly how LVM administrators relocate data between physical drives. The community garden association keeps a map (the metadata) of which plots are in which garden and how the beds are laid out. Without the initial registration of plots as physical volumes, you could not combine them or move the beds around easily.
Why This Term Matters
Physical volumes are the foundational layer in modern storage management, and understanding them is critical for any IT professional who manages servers, cloud infrastructure, or virtualized environments. Without physical volumes, you are limited to traditional disk partitioning, where resizing a partition often requires backing up data, deleting the partition, creating a new one, and restoring the data. This process is time-consuming and carries risk. Physical volumes enable dynamic storage allocation, allowing administrators to add new disk space to a running system without downtime, or to migrate data off a failing drive by moving physical extents to another physical volume in the same volume group.
In enterprise environments, physical volumes are the key to flexibility. For example, when a database server runs out of space, an administrator can attach a new physical volume to the volume group and extend the logical volume that holds the database files, all while the database remains online. This capability is essential for high-availability systems where downtime must be minimized. Physical volumes also underpin snapshot technologies, which allow point-in-time copies of logical volumes for backup or testing. These snapshots rely on the volume manager tracking changes at the physical extent level.
physical volumes enable storage consolidation. Instead of managing multiple separate disks with separate filesystems (like /data1, /data2, /data3), you can pool all disks into one volume group and create logical volumes with the names and sizes you need. This simplifies backup, monitoring, and capacity planning. Even in cloud environments, the concept persists: cloud block storage volumes are often attached to virtual machines as physical volumes that are then combined into volume groups for flexibility. Mastering physical volumes is not just about passing an exam; it is about being able to design and manage resilient, scalable storage systems in real-world IT.
How It Appears in Exam Questions
Physical volume questions in IT certification exams often take the form of scenario-based tasks, configuration sequences, and troubleshooting challenges. A typical scenario might present a system administrator who has added a new hard drive to a server and needs to make the space available to the existing database logical volume. The correct sequence is: use fdisk or parted to create a partition on the new disk, then run pvcreate on that partition, followed by vgextend to add the new physical volume to the volume group, and finally lvextend to grow the logical volume. Questions may ask you to choose the correct order from a list, or to identify which command is missing from a given sequence.
Another common question pattern involves displaying information about physical volumes. You may be asked: Which command shows the amount of free physical extents on a physical volume? The answer is pvs or pvdisplay. A related question might show the output of pvs and ask you to interpret it, such as determining which physical volume has the most free space or identifying a physical volume that is not assigned to any volume group. These questions test your ability to read and understand command output.
Configuration questions may require you to create a physical volume on a specific device, like /dev/sdb, with a particular physical extent size. The command would be pvcreate --dataalignment 1024k /dev/sdb (if aligning for performance). Other questions ask about removing a physical volume from a volume group while it is still in use. The correct procedure is to use pvmove to relocate all physical extents to another physical volume, then vgreduce to remove the physical volume, and finally pvremove to clear the LVM metadata. Exam questions often include a distractor where the candidate tries to use pvremove directly, which would fail because the PV is still part of a VG.
Troubleshooting questions might describe a scenario where a logical volume cannot be extended even though there is space in the volume group. The root cause could be that the physical volume on which the logical volume resides has no free extents, and the volume group has other physical volumes with free space. The solution is to use lvextend with the --alloc anywhere flag or to specify a different physical volume. Another troubleshooting scenario involves a system that fails to boot because a physical volume is missing, causing the volume group to be incomplete. The candidate must know how to use vgscan and vgchange -ay to activate the volume group if the missing physical volume is not critical, or how to replace the failed physical volume. These questions test both conceptual understanding and practical command knowledge.
Practise Physical volume Questions
Test your understanding with exam-style practice questions.
Example Scenario
You are a junior system administrator at a small company that runs a customer relationship management (CRM) application on a Linux server. The CRM stores all its data in a database that lives on a logical volume called lv_data. The logical volume is part of a volume group named vg_app, which currently contains two physical volumes: one 50 GB drive at /dev/sda and one 100 GB drive at /dev/sdb. The lv_data volume is 80 GB, and it is completely full. The company has purchased a new 200 GB hard drive, and you need to add its space to lv_data so the CRM can continue to grow.
You physically install the new drive into the server and boot it up. The new drive appears as /dev/sdc. Your first step is to create a physical volume on it using the command pvcreate /dev/sdc. This command writes the LVM metadata to the new drive, making it ready to join a volume group. Next, you need to add this new physical volume to the existing volume group vg_app. You run vgextend vg_app /dev/sdc. Now, the volume group has a total capacity of 350 GB (50 + 100 + 200) but the logical volume is still only 80 GB.
To make use of the new space, you extend the logical volume lv_data. You run lvextend -L +150G /dev/vg_app/lv_data, which grows the logical volume by 150 GB, for a total of 230 GB. Finally, you need to inform the filesystem about the new space. Since the filesystem is likely ext4, you run resize2fs /dev/vg_app/lv_data. This command resizes the filesystem to match the logical volume size. After that, the CRM database has plenty of room to grow. In this scenario, the physical volume /dev/sdc was the entry point for adding new storage. Without it, you could not have expanded the capacity dynamically.
Common Mistakes
Confusing physical volume with logical volume
A physical volume is a raw block device initialized for LVM, while a logical volume is a virtual block device created from the extents of physical volumes. They serve different roles in the LVM hierarchy.
Always remember the order: physical volume is the base, volume group is the pool, logical volume is the final usable device.
Creating a filesystem directly on a physical volume instead of a logical volume
A physical volume is not meant to mount directly. It contains LVM metadata, not a filesystem. Writing a filesystem on it will overwrite the metadata and break LVM functionality.
Always create logical volumes on a volume group, then put the filesystem on the logical volume, not on the physical volume.
Assuming all physical volumes in a volume group must be the same size
Physical volumes can be of different sizes. Each one contributes its physical extents to the volume group pool. The logical volume can use extents from any physical volume, regardless of size.
You can mix different sized drives in a volume group. Just be aware of performance if you stripe across unbalanced sizes.
Forgetting to resize the filesystem after extending a logical volume
Extending the logical volume only adds space at the block level. The filesystem does not automatically recognize this new space. Without resizing the filesystem, the additional space remains unusable.
Always run the appropriate filesystem resize command (e.g., resize2fs for ext4, xfs_growfs for XFS) after extending the logical volume.
Trying to remove a physical volume that is still in use by a volume group without moving its data first
If a physical volume contains allocated extents, removing it will corrupt the logical volumes that use those extents. The system will lose data.
Use pvmove to relocate all extents from the physical volume to another one in the volume group, then use vgreduce to remove it, and finally pvremove to clean it.
Exam Trap — Don't Get Fooled
{"trap":"The exam question asks: 'Which command removes a physical volume from a volume group?' and the answer choices include 'pvremove /dev/sdb'.","why_learners_choose_it":"Learners see the word 'remove' and think 'pvremove' is the right command because the prefix 'pv' matches physical volume."
,"how_to_avoid_it":"Remember that pvremove only removes the LVM metadata from a device after it has been removed from the volume group. To actually take a PV out of a VG, you must first use pvmove to relocate its data, then vgreduce to remove it from the VG, and only then use pvremove to clear the label."
Commonly Confused With
A logical volume is a virtual block device created from physical extents within a volume group. It acts like a partition and can hold a filesystem. In contrast, a physical volume is the raw device that contributes extents to the pool. You create filesystems on logical volumes, not on physical volumes.
If physical volumes are the ingredients in a kitchen, a logical volume is the cake you bake from those ingredients.
A partition is a contiguous section of a disk created by a partitioning tool like fdisk. A physical volume can be created on a partition, or on a whole disk without partitions. While a partition is a static division, a physical volume is a dynamic building block that can be added to a volume group and resized flexibly.
A partition is like a fenced section of a field. A physical volume is that same field after it has been surveyed and registered with a land office for flexible use.
A volume group is a pool of storage that combines one or more physical volumes. It is the middle layer between physical volumes and logical volumes. Physical volumes are the components that make up a volume group; the volume group itself does not hold data directly. Logical volumes are carved out of the volume group.
If physical volumes are individual bricks, a volume group is the pile of bricks you have collected. The logical volume is the wall you build from those bricks.
Step-by-Step Breakdown
Identify the device
First, determine which block device you want to use as a physical volume. This can be a whole disk (e.g., /dev/sdb) or a partition (e.g., /dev/sdc1). Use commands like lsblk, fdisk -l, or blkid to list available devices and ensure the device is not already in use or mounted.
Create the physical volume
Run pvcreate /dev/sdX (where X is the device identifier). This writes LVM metadata to the device, including a UUID, the physical extent size (default 4 MiB in LVM2), and a placeholder for volume group information. The device is now initialized as a physical volume.
Verify the physical volume
Use pvs or pvdisplay to confirm the physical volume was created successfully. These commands show the device name, size, free extents, and the volume group it belongs to (if any). Verifying helps catch mistakes like writing over an existing filesystem.
Add the physical volume to a volume group
If you have an existing volume group, run vgextend VolumeGroupName /dev/sdX. If creating a new volume group, use vgcreate VolumeGroupName /dev/sdX. This step pools the physical volume's extents with others in the group.
Allocate space from the physical volume
Create or extend a logical volume using lvcreate or lvextend. The volume manager allocates physical extents from the physical volume you added. You can control which physical volume to use with the --alloc or --stripes options for performance or redundancy.
Mount the logical volume
Create a filesystem on the logical volume (e.g., mkfs.ext4 /dev/VgName/LvName), then mount it to a directory. The physical volume remains in the background, providing the raw storage blocks through the volume group.
Practical Mini-Lesson
In real-world IT, physical volumes are the first step in building flexible storage. Imagine you are setting up a new web server. You have two 500 GB SSDs. Instead of using them as separate mount points (/data1 and /data2), you want a single 1 TB pool that you can carve into logical volumes for web content, logs, and a database. The process begins by initializing each SSD as a physical volume with pvcreate /dev/sda and pvcreate /dev/sdb. Then you create a volume group with vgcreate vg_web /dev/sda /dev/sdb. Now you have a pool of 1 TB. From this pool, you create a 200 GB logical volume for the website (lv_www), a 100 GB volume for logs (lv_logs), and a 400 GB volume for the database (lv_db). You can leave the remaining 300 GB free for future growth.
What professionals need to know is that physical volumes are not just for LVM on Linux. They are analogous to physical disks in Windows Storage Spaces, where you add a disk to a storage pool (similar to creating a PV and adding it to a VG). In cloud environments, when you attach an EBS volume to an EC2 instance, you can initialize it as a physical volume and add it to a volume group, exactly as you would on-premises. This consistency across platforms makes the concept universally valuable.
A common configuration detail is the physical extent size. By default, LVM2 uses 4 MiB extents, but for large volumes or specific performance needs, you might change this size when creating the physical volume with pvcreate --setphysicalvolumesize. A larger extent size reduces metadata overhead but increases the minimum allocation unit. For example, a 4 MiB extent means the smallest logical volume you can create is 4 MiB, and any space is allocated in 4 MiB chunks.
What can go wrong? Common issues include device name changes after reboot (when using /dev/sdX names, which can change), misalignment causing poor performance, and forgetting to update the initramfs after adding a physical volume containing the root filesystem. To avoid device name issues, use persistent device names like /dev/disk/by-id/ or /dev/disk/by-uuid/. For alignment, ensure your physical volume starts at a multiple of the underlying disk’s alignment (e.g., 1 MiB boundary for modern SSDs) to avoid read-modify-write penalties. If the physical volume holds part of the root logical volume, you must rebuild the initramfs with dracut or mkinitrd so the system can find the PV during boot. Knowing these practical details is what separates an exam passer from a real sysadmin.
Physical Volume Lifecycle in LVM
In Logical Volume Manager (LVM) environments, a physical volume (PV) is the foundational building block. It represents a storage device-such as a hard disk partition, an entire hard disk, or a RAID array-that has been initialized for use by LVM. Understanding the lifecycle of a physical volume is critical for system administrators and frequently appears in certification exams like CompTIA Linux+, Red Hat Certified System Administrator (RHCSA), and Linux Professional Institute (LPI) certifications.
The lifecycle begins when an administrator selects a block device to transform into a PV. The device must be available and not contain any existing LVM metadata. Using the command 'pvcreate', the system writes LVM metadata to a specific area (commonly at the start of the device). This metadata includes a UUID (Universally Unique Identifier), the size of the device, and information about which volume group (VG) the PV belongs to. Once created, the PV enters an 'active' state, meaning it is ready to be added to a volume group.
After creation, the PV is typically added to a volume group using 'vgextend'. This step pools the physical extents (PEs) from the PV into the VG’s free extent pool. Physical extents are fixed-size chunks of storage (default 4 MiB) that LVM uses as the smallest allocatable units. The PV now contains metadata linking it to the VG, and its extents become available for logical volumes (LVs). If the PV is later removed from the VG using 'vgreduce', it reverts to being a standalone PV (still active but unallocated).
The PV can be moved while retaining its data. Administrators often use 'pvmove' to relocate physical extents from one PV to another within the same volume group-this is commonly done to prepare a PV for removal or to replace a failing disk. During a move, the PV remains part of the VG but temporarily holds data that is in transit.
Eventually, a PV may need to be decommissioned. If the PV is part of a VG, it must be removed using 'vgreduce' first (or the entire VG can be destroyed). If the PV is no longer needed, the administrator can use 'pvremove' to wipe the LVM metadata from the device, returning it to a raw, uninitialized state. This step is essential before repurposing the disk for non-LVM usage.
Certification exams often test the sequence of these steps. For example, a question might ask which command deactivates a PV without destroying data-the answer is 'pvchange -a n /dev/sdX1', which sets the PV to inactive state within the volume group. Another common test involves understanding that a PV cannot be removed from a VG if it still holds allocated extents; it must have all its extents moved using 'pvmove' first. The physical volume lifecycle also ties directly to disk failure scenarios. If a PV becomes faulty, administrators must use 'pvck' to check metadata consistency. In production, redundant PVs (via RAID) are recommended to avoid single points of failure.
the PV lifecycle includes creation ('pvcreate'), addition to VG ('vgextend' or 'vgcreate'), data migration ('pvmove'), state management ('pvchange'), and final removal ('pvremove' or 'vgreduce'). Each step has specific prerequisites and consequences that exam questions exploit to test practical, real-world understanding. Mastery of these states and commands ensures high availability and efficient storage management in enterprise Linux environments.
Physical Volume Metadata and UUID Management
Every physical volume (PV) in LVM is uniquely identified by a metadata area that contains a universally unique identifier (UUID), the device size, the volume group membership, and configuration parameters. This metadata is crucial for LVM’s ability to recognize and manage storage across diverse hardware environments, and it is a frequent focus in certification exams such as RHCSA, LPI, and LPIC-1.
When a device is initialized as a PV using 'pvcreate', LVM writes a metadata header to a reserved area-typically at the beginning of the device (in the first 4 KiB). The header contains the UUID (a 128-bit number rendered as a hex string), the version of the LVM metadata format, and a pointer to the location of the remainder of the metadata. The metadata itself is stored in a text-based format (or in LVM2 format) that lists all physical extents and their allocation status.
One of the most important exam topics is how to view and verify PV metadata. The command 'pvdisplay /dev/sdb1' shows detailed information, including PV name, UUID, size, allocated extents, free extents, and the associated volume group. The 'pvs' command provides a concise, table-format output that is often used for scripting and quick checks. For example, 'pvs --noheadings -o pv_name,vg_name' can list all PVs and their VGs without extra formatting. Exams test whether candidates understand that a PV can be identified by its UUID even if the device name changes (e.g., after a reboot due to drive reordering). This is a common scenario: booting from a different kernel or adding disks may reassign device names, but LVM relies on UUIDs to maintain consistency.
Another key concept is metadata duplication. LVM stores multiple copies of the metadata on each PV to prevent corruption. By default, two copies are retained (or more if configured). The 'pvck' command validates the metadata structure and can repair some types of corruption. If metadata is lost or damaged, 'pvcreate --uuid <original_uuid> --restorefile <backup_file> /dev/sdX' can be used to reinitialize a PV with its original UUID and metadata, restoring the device to its previous state. This emergency recovery technique appears in advanced exam questions.
When a PV is part of a volume group, the VG metadata also resides on the PV. This VG metadata includes the names and configuration of all logical volumes. Therefore, losing all PVs in a VG means losing the volume group; but if at least one PV remains, the VG can be partially recovered. To back up metadata, administrators should use 'vgcfgbackup' regularly; the backup is typically stored in /etc/lvm/backup. The command 'vgcfgrestore' can restore both VG and PV metadata from these files.
Certification exams often include troubleshooting questions where candidates must identify why a PV is not recognized. Common causes include missing UUIDs (e.g., after a disk failure), metadata area overwritten by other partitioning tools, or UUID collision (rare but possible with cloning). The correct approach is to run 'pvs -a' to discover all devices with LVM metadata, then use 'pvck -v /dev/sdX' to inspect metadata details.
PV metadata and UUIDs ensure device-independent identification and robust recovery. Exam questions test command syntax ('pvdisplay', 'pvs', 'pvck'), understanding of metadata locations, and recovery procedures. Knowing how to interpret the output and troubleshoot missing PVs is considered essential for any storage certification. Administrators who master these concepts can confidently manage LVM storage in both lab and production settings.
Memory Tip
Physical volume = the brick, volume group = the pile of bricks, logical volume = the wall. Always start with the brick.
Learn This Topic Fully
This glossary page explains what Physical volume means. For a complete lesson with labs and practice, see the topic guide.
Covered in These Exams
Current Exam Context
Current exam versions that test this topic — use these objectives when studying.
XK0-006CompTIA Linux+ →220-1101CompTIA A+ Core 1 →Related Glossary Terms
A 2-in-1 laptop is a portable computer that can switch between a traditional laptop form and a tablet form, usually by detaching or rotating the keyboard.
The 24-pin motherboard connector is the main power cable that connects the computer's power supply unit (PSU) to the motherboard, supplying electricity to the motherboard and its components.
Two-factor authentication (2FA) is a security method that requires two different types of proof before granting access to an account or system.
A 3D printer is a device that creates physical objects by depositing layers of material based on a digital model.
5G is the fifth generation of cellular network technology, designed to deliver faster speeds, lower latency, and support for many more connected devices than previous generations.
The 8-pin CPU connector is a power cable from the power supply that delivers dedicated electricity to the processor on a computer's motherboard.
802.1Q is the networking standard that allows multiple virtual LANs (VLANs) to share a single physical network link by tagging Ethernet frames with VLAN identification information.
802.1X is a network access control standard that authenticates devices before they are allowed to connect to a wired or wireless network.
Quick Knowledge Check
1.Which command initializes a block device as an LVM physical volume?
2.What is the purpose of the 'pvmove' command?
3.What must be true before using 'pvremove' on a device?
4.How does LVM uniquely identify a physical volume even if the device name changes?
5.Which command shows detailed information including the UUID and volume group of a physical volume?
Frequently Asked Questions
Can I create a physical volume on an entire disk without partitioning first?
Yes, you can create a physical volume directly on a whole disk like /dev/sdb. This is common in LVM setups, but be aware that tools like fdisk may show no partition table. Some systems prefer a partition for clarity, but it is not required.
What happens if I run pvcreate on a device that already has a filesystem?
The pvcreate command will overwrite the filesystem metadata at the beginning of the device, making the existing data unrecoverable. LVM will warn you, and you must confirm the operation. Always double-check the device before running pvcreate.
How do I see which physical volumes are present on my system?
Use the pvs command for a concise list of all physical volumes, including their size and volume group membership. For more details, use pvdisplay [device].
Can I resize a physical volume?
You can resize a physical volume if the underlying device has been resized (e.g., after expanding a virtual disk in a hypervisor). Use pvresize /dev/sdX to update the PV to the new device size. This does not affect existing data.
Is it possible to move a physical volume to another volume group?
Yes, but only if the physical volume is not currently allocated to any logical volume. You can remove it from the current volume group using vgreduce and then add it to another with vgextend. If it contains data, use pvmove first to relocate the extents.
Why does my physical volume show as duplicate in pvs output?
A duplicate PV error typically occurs when the same disk is accessible via multiple device paths (e.g., /dev/sdb and /dev/disk/by-id/xxx). LVM sees the same UUID twice. This can happen in virtualization or multipath environments. Use the device filter in lvm.conf to exclude one path.
Summary
A physical volume is the foundational storage unit in logical volume management systems, representing a block device that has been initialized with metadata for use by a volume manager. It is the first step in creating flexible, resizable storage pools that can be dynamically allocated across multiple drives. Understanding physical volumes is essential for IT professionals because they enable online storage expansion, data migration, snapshots, and efficient space utilization, all without the downtime associated with traditional partition resizing.
In certification exams, physical volumes are tested through command sequences, scenario-based troubleshooting, and interpretation of command output. Common mistakes include confusing physical volumes with logical volumes, writing filesystems directly on physical volumes, and forgetting to resize the filesystem after extending a logical volume. The key exam trap is thinking that pvremove alone removes a physical volume from a volume group, when in fact you must first move its data with pvmove and remove it with vgreduce.
The takeaway for learners is to internalize the hierarchy: physical volume to volume group to logical volume. Memorize the key commands (pvcreate, pvdisplay, pvs, pvmove, pvremove) and their purposes. Practice creating scenarios where you add a disk, initialize it as a PV, add it to a VG, and create or extend an LV. With this foundation, you will be prepared for both exam questions and real-world storage management challenges.