Question 220
A student has implemented the following configuration: Two fresh disposable LVM partitions must become one storage pool for a new application. What repeatable control best reduces regressions or unsafe changes?
Explanation
Correct Answer
Use descriptive VG names and verify physical member lists before changes. This guards against recurrence of: A volume group aggregates free extents from one or more physical volumes. Confirm the lab's final state by: `vgs vg_training` displays the total size and `pvs` maps both PVs to the group.
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: A volume group aggregates free extents from one or more physical volumes.
Check `vgs` free extents before provisioning and keep names consistent with service inventory. That control is best suited to a separate scenario: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. It is not the best safeguard for the current mechanism: A volume group aggregates free extents from one or more physical volumes.
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 aggregates free extents from one or more physical volumes.