XK0-005 · Question #138
An administrator is troubleshooting an application that has failed to start after the server was rebooted. Noticing the data volume is not mounted, the administrator attempts to mount it and…
The correct answer is A. The logical volume is not active. The administrator should make it active with. The application failed to start because the data volume is not mounted, and the logical volume status indicates it is inactive.
Question
An administrator is troubleshooting an application that has failed to start after the server was rebooted. Noticing the data volume is not mounted, the administrator attempts to mount it and receives this error:
Upon checking the logical volume status, the administrator receives this information:
Which of the following can be said about the data logical volume, and how can this problem be resolved?
Options
- AThe logical volume is not active. The administrator should make it active with
- BThe logical volume file system has become corrupted. The administrator should repair it with
- CThe logical volume is OK but the /dev special files are missing. The administrator should
- DThe file system is read-only. The administrator should remount it as read-write with the command
How the community answered
(63 responses)- A79% (50)
- B6% (4)
- C11% (7)
- D3% (2)
Why each option
The application failed to start because the data volume is not mounted, and the logical volume status indicates it is inactive.
The `lvdisplay` output implies the logical volume is not active, which prevents it from being mounted. The administrator should activate the logical volume using the `lvchange -ay <logical_volume_path>` command to make it available for mounting.
While filesystem corruption can prevent mounting, the problem description directly points to the logical volume's activation status rather than filesystem integrity.
The `/dev` special files for logical volumes are dynamically created when the logical volume is active, so missing files are a symptom of an inactive LV, not the primary issue.
A read-only filesystem would still allow mounting, but restrict write operations; the core problem here is the inability to mount the volume at all due to its inactive state.
Concept tested: LVM logical volume activation
Source: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/logical_volume_manager_administration/lv_activation
Topics
Community Discussion
No community discussion yet for this question.