Make a point-in-time view of an LV within the same VG for a short backup window.
Assume copy-on-write tracking of blocks changed in the origin LV.
Which description is appropriate?
An LVM snapshot provides a point-in-time view using copy-on-write. It is not an independent backup against storage failure, and its space and performance impact must be monitored.
Detailed explanation
Incorrect. A normal snapshot does not immediately duplicate every origin block to another disk.
Correct. Copy-on-write preserves pre-change blocks for a point-in-time view.
Incorrect. Combining PVs into a VG is the role of VG management.
Incorrect. Registering a UEFI bootloader is unrelated to LVM snapshots.
Try it yourself
An example you can run in a temporary verification environment.
lvcreate --help 2>&1 | grep -E -- '--snapshot|-s' | sed -n '1,4p'Expected result
スナップショット作成用-sまたは--snapshotの説明Key points
- Provides a point-in-time view
- Tracks changed origin blocks
- It is not an independent backup
Notes
- Environment: LVM2 / ヘルプ表示のみ
- Use read-only inspection or a disposable disk when learning storage commands.
- Partition and LVM writes can destroy data; verify the target before running them.
Foundation review
Place the operation
An LVM snapshot can support short-lived backup workflows but does not isolate data from failure of the same storage.
Check the side effect
Monitor snapshot fullness and copy data to independent storage for durable backup.