Rather than an /etc/fstab line, you want systemd to manage a mount at /srv/data with its own unit file. What must that unit file be called for systemd to accept it?
LPIC-1 Exam 101-500, objective 104. Devices, Linux filesystems, filesystem hierarchy standard hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Correct srv-data.mount
Correct. A mount unit's name must be the escaped mount-point path: leading and trailing slashes dropped, remaining slashes turned into dashes, plus the .mount suffix.
Not correct srv.data.mount
Wrong separator. A dot is an ordinary character in an escaped path name, so systemd would read this as a mount point that does not match the unit's Where= setting and refuse to load it.
Not correct data.mount
Wrong. data.mount is the unit name for the mount point /data. The whole path must be encoded, not just the last component.
Not correct srv-data.service
Wrong unit type. A .service unit describes a process to run; mounting is expressed by the .mount unit type, whose Where=, What= and Type= settings correspond to the fstab fields.
Why
systemd derives a mount unit's name from its mount point by path escaping, so /srv/data becomes srv-data.mount and the unit's Where= must match that name exactly or the unit is rejected. `systemd-escape -p --suffix=mount /srv/data` produces the name mechanically, which matters once a path contains characters that need \x2d style escapes. Ordinary fstab entries are not a separate mechanism: systemd-fstab-generator converts each of them into an equivalent mount unit at boot, which is why fstab options such as noauto and nofail keep working.
Where this comes from
- Cited
- manual page systemd.mount(5)
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 104 and space the ones you get wrong.
More questions on this objective
- A new disk /dev/sdb has no partition table at all. Which command writes an empty GPT partition table onto it without dropping you into an interactive editor? machine-checked
- You need the partition /dev/sdc1 on a USB stick to carry a FAT32 filesystem so that Windows machines can read and write it. Which command creates it? machine-checked
- You have just run `mkswap /dev/sdb2`. Which command makes the kernel start using that swap area immediately, without a reboot? machine-checked
- Why is it dangerous to run e2fsck against an ext4 filesystem that is currently mounted read-write? machine-checked
- On an ext4 filesystem at /dev/sda1 you want an automatic check to be forced after every 30 mounts. Which command sets that? machine-checked
- `df -h /var` reports the filesystem 100% full, but `du -sh /var` accounts for only about half that space. Nothing is hidden under a mount point. What is the most likely explanation? machine-checked
All questions on Devices, Linux filesystems, filesystem hierarchy standard