XK0-005 · Question #684
XK0-005 Question #684: Real Exam Question with Answer & Explanation
The correct answer is A: umount /app. The outputs indicate that the filesystem /app mounted on /dev/sdc1 is in a read-only state, which prevents users from writing to it (as seen in Output 1). The read-only state (ro) in Output 2 suggests that the filesystem was automatically remounted as read-only due to an error, w
Question
The users of a Linux system are unable to use one of the application filesystems. The following outputs have been provided: Output 1: $ cd /app $ touch file touch: cannot touch 'file': Read-only file system Output 2: /dev/sdc1 on /app type ext4 (ro,relatime,seclabel,data=ordered) Output 3: /dev/sdc1 /app ext4 defaults 0 0 Output 4: [ 302.048075 ] Buffer I/O error on dev sdc1, logical block 0, asyng page read [ 302.048490 ] EXT4-fs (sdc1): Attempt to read block from filesystem resulted in short read while trying to re-open /dev/sdc1 Which of the following actions will resolve this issue?
Options
- Aumount /app
- Bxfs_repair /dev/sdc1
- Cumount /app
- Dfsck -y /dev/sdc1
Explanation
The outputs indicate that the filesystem /app mounted on /dev/sdc1 is in a read-only state, which prevents users from writing to it (as seen in Output 1). The read-only state (ro) in Output 2 suggests that the filesystem was automatically remounted as read-only due to an error, which is confirmed by the buffer I/O error message and the EXT4 short read errors shown in Output 4. To resolve this issue: 1. Unmount the Filesystem: First, unmount so that filesystem checks can be performed 2. Run Filesystem Check (fsck): Since /dev/sdc1 is an ext4 filesystem, the correct tool to repair it is fsck. Running fsck with the -y flag will automatically answer "yes" to any prompts, ensuring that errors are fixed. fsck -y /dev/sdc1 3. Remount the Filesystem: Once fsck has completed successfully, remount the filesystem
Topics
Community Discussion
No community discussion yet for this question.