Question 380
A student has implemented the following configuration: An online lab volume needs another 1 GiB of block capacity but its administrator attempts to grow the filesystem without changing the LV. What repeatable control best reduces regressions or unsafe changes?
Explanation
Correct Answer
Plan LV resizing and compatible filesystem growth as separate verified steps. This guards against recurrence of: Logical volume capacity and filesystem capacity are distinct layers. Confirm the lab's final state by: `lvs /dev/vg_training/lv_db` reports the larger block size; `df` may still show old filesystem capacity until filesystem growth.
Incorrect Answers
Require unmount, backup and dependency review before LV retirement. That control is best suited to a separate scenario: A test operator removed a block LV without first unmounting it, risking a busy-device error or data loss. It is not the best safeguard for the current mechanism: Logical volume capacity and filesystem capacity are distinct layers.
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: Logical volume capacity and filesystem capacity are distinct layers.
Monitor free-extents capacity and set thresholds before service expansion. That control is best suited to a separate scenario: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. It is not the best safeguard for the current mechanism: Logical volume capacity and filesystem capacity are distinct layers.