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

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?

Accepted Answer

A. The logical volume is not active. The administrator should make it active with lvchange -ay LVM logical volumes can be in an inactive state after a reboot if volume group auto-activation is disabled or fails. The lvchange -ay command sets the logical volume to active state, making the block device available so the filesystem can be mounted normally.

Answer

B. The logical volume file system has become corrupted. The administrator should repair it with Filesystem corruption would still allow the volume to appear active in lvs output and typically produces different errors such as journal recovery failures; fsck repairs corruption but cannot fix an inactive volume.

Answer

C. The logical volume is OK but the special files are missing. The administrator should Missing device special files under /dev produce a 'no such file or directory' error rather than a state-related mount failure, and are regenerated by udev or vgscan --mknodes, not by activating the volume.

Answer

D. The file system is read-only. The administrator should remount it as read-write with the command A read-only filesystem would still mount successfully with the 'ro' flag and would not cause the volume to show as inactive in lvs output; remounting read-write does not resolve an inactive logical volume.

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