Question 340
For this Linux administration lab: An existing volume group needs more capacity, and a new dedicated blank PV has been attached. Which safety and lifecycle check best prevents the same problem returning?
Explanation
Correct Answer
Track approved PV additions in capacity records and test before growing filesystems. This guards against recurrence of: A volume group does not gain capacity just because a new disk is visible to Linux. Confirm the lab's final state by: `vgs vg_training` reports increased free space and `pvs` shows the new member assigned.
Incorrect Answers
Confirm exact partition number, holders and backups before partition deletion. That control is best suited to a separate scenario: A trainee needs to delete one unused partition on a disposable GPT disk but proposes erasing the whole disk. It is not the best safeguard for the current mechanism: A volume group does not gain capacity just because a new disk is visible to Linux.
Plan LV resizing and compatible filesystem growth as separate verified steps. That control is best suited to a separate scenario: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. It is not the best safeguard for the current mechanism: A volume group does not gain capacity just because a new disk is visible to Linux.
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: A volume group does not gain capacity just because a new disk is visible to Linux.