Question 300
A student has implemented the following configuration: An LV should consume precisely 20% of remaining free extents for a training scratch workload. What repeatable control best reduces regressions or unsafe changes?
Explanation
Correct Answer
Document whether requests are byte sizes or extents before provisioning LVM. This guards against recurrence of: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`. Confirm the lab's final state by: `lvs` and `vgs` show the LV allocation as the expected fraction of previously free extents.
Incorrect Answers
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: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.
Verify extent allocation and redundancy before any VG reduction. That control is best suited to a separate scenario: A dedicated LVM physical volume is no longer used by any allocated extents but remains listed in a training VG. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.
Treat unexpected signatures as a stop-and-investigate condition, never automatic wipe permission. That control is best suited to a separate scenario: A lab disk appears to contain an old filesystem signature after a supposedly blank virtual disk is attached. It is not the best safeguard for the current mechanism: `-l` allocates extents and supports percentage modifiers, unlike the size option `-L`.