Question 180
For this Linux administration lab: A blank LVM lab partition `/dev/vdb1` exists but cannot be added to a volume group until initialized. Which safety and lifecycle check best prevents the same problem returning?
Explanation
Correct Answer
Inspect device signatures and mount holders before PV creation. This guards against recurrence of: LVM physical volumes carry metadata that lets volume groups manage underlying extents. Confirm the lab's final state by: `pvs /dev/vdb1` shows a physical volume and no other disk was initialized.
Incorrect Answers
Include a full storage dependency diagram in change requests. That control is best suited to a separate scenario: An operator confuses a partition number with an LVM logical volume name when looking for a mounted database. It is not the best safeguard for the current mechanism: LVM physical volumes carry metadata that lets volume groups manage underlying extents.
Use stable UUID or labels for persistent mounts and run `findmnt --verify` before reboot. That control is best suited to a separate scenario: A server has an approved lab LV mounted through `/dev/vdb1` and the device name changes after adding another disk. It is not the best safeguard for the current mechanism: LVM physical volumes carry metadata that lets volume groups manage underlying extents.
Make disk identification a mandatory gate; never run `mklabel` on a disk with live data. That control is best suited to a separate scenario: The disposable blank `/dev/vdb` has no partition table, but the lab task needs a GPT disk layout. It is not the best safeguard for the current mechanism: LVM physical volumes carry metadata that lets volume groups manage underlying extents.