You run `ln /data/report.txt /data/backup.txt` and then `rm /data/report.txt`. What is the state of the data afterwards?
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
Not correct The data is gone, because rm always frees the file's blocks immediately.
Wrong. rm calls unlink(), which removes one name. Blocks are released only when the last name and the last open descriptor are gone.
Not correct /data/backup.txt is now a dangling link and reading it fails with 'No such file or directory'.
Wrong — that is symbolic link behaviour. A symlink stores a path, so deleting the target breaks it. A hard link stores nothing but a name pointing at an inode.
Correct The data is fully intact and reachable through /data/backup.txt; the inode's link count simply dropped from 2 to 1.
Correct. Both names always pointed at the same inode. rm removes a directory entry and decrements the link count; the blocks are freed only when the count reaches 0 and no process holds the file open.
Not correct /data/backup.txt still exists but is now an empty file of zero bytes.
Wrong. Nothing truncates the inode. Its size, contents, permissions and timestamps are unchanged; only the link count in the inode changed.
Why
A hard link is an additional directory entry pointing at the same inode, so all names are equally 'the file' — there is no original. `ls -l` shows the link count in the second column, and `ls -i` shows that the names share one inode number. Hard links cannot span filesystems (inode numbers are only unique within one) and ordinary users cannot create them to directories.
Where this comes from
- Cited
- LPI exam objective 104.6
- What it says
- Create hard links and understand how they differ from symbolic links.
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