Question 460
A student has implemented the following configuration: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. What repeatable control best reduces regressions or unsafe changes?
Explanation
Correct Answer
Verify extent allocation and redundancy before any VG reduction. This guards against recurrence of: A PV cannot be safely removed from a VG while it still contains required extents. Confirm the lab's final state by: `pvs` shows the retired PV is no longer a member and the VG remains healthy.
Incorrect Answers
Perform non-destructive detection before initializing any storage metadata. That control is best suited to a separate scenario: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. It is not the best safeguard for the current mechanism: A PV cannot be safely removed from a VG while it still contains required extents.
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 PV cannot be safely removed from a VG while it still contains required 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: A PV cannot be safely removed from a VG while it still contains required extents.