Which command sequence creates a new LVM physical volume on /dev/sdb1 and then creates a volume group named vg_data using that PV?

Prepare for the Red Hat Certified Systems Admin Exam EX200. Enhance your skills with interactive quizzes, flashcards, and detailed explanations. Ace your certification exam today!

Multiple Choice

Which command sequence creates a new LVM physical volume on /dev/sdb1 and then creates a volume group named vg_data using that PV?

Explanation:
Initializing the device as a physical volume is the essential first step. pvcreate /dev/sdb1 marks that disk or partition as a physical volume that LVM can manage. Without doing this, the device cannot participate in any volume group. Once the PV is prepared, you create a new volume group that uses that PV with vgcreate vg_data /dev/sdb1. This defines a brand-new VG named vg_data and attaches the initialized PV to it, making the space available for logical volumes. The order is important: you can’t form a new VG from an uninitialized PV, so pvcreate must come first. Using vgextend would only add a PV to an existing VG, not create a new one, and vgchange merely activates or deactivates an existing VG rather than creating it.

Initializing the device as a physical volume is the essential first step. pvcreate /dev/sdb1 marks that disk or partition as a physical volume that LVM can manage. Without doing this, the device cannot participate in any volume group.

Once the PV is prepared, you create a new volume group that uses that PV with vgcreate vg_data /dev/sdb1. This defines a brand-new VG named vg_data and attaches the initialized PV to it, making the space available for logical volumes.

The order is important: you can’t form a new VG from an uninitialized PV, so pvcreate must come first. Using vgextend would only add a PV to an existing VG, not create a new one, and vgchange merely activates or deactivates an existing VG rather than creating it.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy