The directory /srv/data lives on its own filesystem and must also appear at /var/www/html/data, where a chrooted web server can reach it. A symbolic link is no use because it points outside the chroot. Which command makes the same directory tree visible at the second location?
LPIC-1 Exam 101-500, objective 104. Devices, Linux filesystems, filesystem hierarchy standard medium
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 mount --bind /srv/data /var/www/html/data
Correct. A bind mount attaches an existing directory tree at a second mount point, so both paths reach the same files through the same filesystem, with no link to follow.
Not correct mount -t bind /srv/data /var/www/html/data
Wrong. There is no filesystem type called bind; binding is requested with the --bind (or -B) operation, not with -t.
Not correct mount -o loop /srv/data /var/www/html/data
Wrong. The loop option wraps a regular file that contains a filesystem image, such as an ISO, in a loop device. Its source is a file, not a directory.
Not correct ln -s /srv/data /var/www/html/data
Wrong for this case. It creates the symlink the question has already ruled out: the stored path /srv/data does not exist inside the chroot, so the link dangles there.
Why
`mount --bind olddir newdir` remounts part of the hierarchy somewhere else; --rbind extends this to the submounts underneath. It is resolved by the kernel's mount table rather than by following a path stored in a link, which is what makes it work inside a chroot or a container root. The persistent form in /etc/fstab uses the source directory as the device field, the type `none`, and the option `bind`.
Where this comes from
- Cited
- manual page mount(8)
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