A data area may need to grow in the future.
Treat several physical devices as a pool and allocate flexible logical areas.
Which design benefit is correct?
LVM pools PV capacity in a VG and makes it easier to add free VG space to an LV. The filesystem must still be expanded separately.
Detailed explanation
Incorrect. Firmware support for booting from arbitrary LVs is not guaranteed by LVM.
Incorrect. Firmware support for booting from arbitrary LVs is not guaranteed by LVM.
Incorrect. Filesystem shrink support depends on the filesystem and procedure.
Incorrect. Filesystem shrink support depends on the filesystem and procedure.
Incorrect. Basic LVM does not automatically replicate data after a disk failure.
Incorrect. Basic LVM does not automatically replicate data after a disk failure.
Correct. Free VG capacity can be added to an LV later, subject to filesystem support.
Correct. Free VG capacity can be added to an LV later, subject to filesystem support.
Try it yourself
An example you can run in a temporary verification environment.
command -v lvs >/dev/null && lvs 2>/dev/null || echo 'LVM metadata is unavailable'Expected result
LV一覧、またはLVM未使用・権限制約の表示Key points
- Allocate from a capacity pool
- LV and filesystem growth are separate
- Normal LVM does not guarantee redundancy
Notes
- Environment: Linux / LVM2
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.