XK0-005 · Question #435
A Linux administrator rebooted a server. Users then reported some of their files were missing. After doing some troubleshooting, the administrator found one of the filesystems was missing. The…
The correct answer is C. Create a mount unit and enable it to be started at boot. Filesystems mounted manually (e.g., via mount command at the CLI) do not persist across reboots because they are not recorded in /etc/fstab or as a systemd unit. To make a mount permanent and automatically applied at boot, the administrator should create a systemd mount unit…
Question
A Linux administrator rebooted a server. Users then reported some of their files were missing. After doing some troubleshooting, the administrator found one of the filesystems was missing. The filesystem was not listed in /etc/f stab and might have been mounted manually by someone prior to reboot. Which of the following would prevent this issue from reoccurring in the future?
Options
- ASync the mount units.
- BMount the filesystem manually.
- CCreate a mount unit and enable it to be started at boot.
- DRemount all the missing filesystems
How the community answered
(33 responses)- A9% (3)
- B3% (1)
- C85% (28)
- D3% (1)
Explanation
Filesystems mounted manually (e.g., via mount command at the CLI) do not persist across reboots because they are not recorded in /etc/fstab or as a systemd unit. To make a mount permanent and automatically applied at boot, the administrator should create a systemd mount unit file (e.g., /etc/systemd/system/opt-app.mount) and enable it with systemctl enable, which creates the appropriate symlinks so systemd mounts it at startup. Simply mounting it manually again solves the immediate problem but recreates the same issue on the next reboot. Syncing mount units or remounting missing filesystems are also temporary measures that do not persist.
Topics
Community Discussion
No community discussion yet for this question.