Question 610
In a hands-on RHCSA practice VM, the assigned outcome was: A newly attached block device is not visible to LVM because it is not yet recognized by the kernel. What specific verification would demonstrate the target state?
Explanation
Correct Answer
The expected device appears under the lab inventory ID and no device is formatted during discovery. This check confirms the expected effect of: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation. It distinguishes the intended result from the original failure mechanism: Device discovery and actual filesystem or LVM creation are separate operations.
Incorrect Answers
The volume group reports sufficient free extents before the successful resize. That verifies a separate lab task: An LV from a disposable VG has no free extents to grow, and the operator repeatedly retries `lvextend`. It does not validate the implementation required here: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation.
`lvs /dev/vg_training/lv_db` reports the requested LV and does not show a filesystem automatically. That verifies a separate lab task: An LVM volume group `vg_training` exists and a test database requires a new 2 GiB logical volume. It does not validate the implementation required here: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation.
The selected disk has no filesystem, partition or mount dependencies and matches the lab's disk ID. That verifies a separate lab task: A disposable VM has several added disks and the operator must identify which blank disk is safe before partitioning. It does not validate the implementation required here: Use `lsblk`, device-rescan methods supported for the VM, and `udevadm settle` before any PV creation.