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?

Question

Accepted Answer

A. The logical volume is not active. The administrator should make it active with When an LVM logical volume is inactive, its device special file (e.g., `/dev/vgname/lvname`) does not exist or is not available, preventing it from being mounted. The `lvchange -ay <logical_volume_path>` command activates the logical volume, making it available for mounting by the system.

Answer

B. The logical volume file system has become corrupted. The administrator should repair it with While filesystem corruption can prevent mounting, the specific error 'logical volume is not active' directly points to an LVM state issue, not necessarily filesystem corruption as the primary problem.

Answer

C. The logical volume is OK but the /dev special files are missing. The administrator should Missing `/dev` special files is a symptom of an inactive logical volume; the cause is the LV's inactive status, not that the files are just arbitrarily missing. Activating the LV would recreate these special files.

Answer

D. The file system is read-only. The administrator should remount it as read-write with the command A read-only filesystem might mount but refuse writes, but the problem here is that the volume is not mounted at all, indicating a more fundamental issue than just permissions.

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…

Question

Exhibit

Options

How the community answered

Why each option

Topics

Community Discussion