Server operations · Lesson 34 of 36 · 8 minutes

Mount and capacity correlation

Connect mounted filesystems, block devices, and available space.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Read mounted filesystems
Run mount.
Hint & worked example
Inspect a synthetic mounted-filesystem table.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
mount
```
Remember: Mount options can affect writability independently of file ownership.
2
Read block devices
Run lsblk.
Hint & worked example
Inspect a synthetic block-device tree.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
lsblk
```
Remember: A device, partition, filesystem, and mount point are different concepts.
3
Read filesystem capacity
Run df -h.
Hint & worked example
Inspect the virtual filesystem capacity report. Real systems can run out of space or inodes independently.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
df -h
```
Remember: Available space is a snapshot, not a guarantee that a later write will succeed.

Understand the pattern

Correlating storage topology with capacity helps operators explain what they know before they change anything.

mount: Inspect a synthetic mounted-filesystem table.
Mount options can affect writability independently of file ownership.
lsblk: Inspect a synthetic block-device tree.
A device, partition, filesystem, and mount point are different concepts.
df: Inspect the virtual filesystem capacity report. Real systems can run out of space or inodes independently.
Available space is a snapshot, not a guarantee that a later write will succeed.

Worked example and expected result

$ mount

lab-root on / type learnfs (rw,simulated)
lab-logs on /var/log type learnfs (rw,simulated)

Exit status: 0. The command completed successfully in the training fixture.

$ lsblk

NAME   SIZE TYPE MOUNTPOINT
learn0  20G disk /
learn1   2G disk /var/log

Exit status: 0. The command completed successfully in the training fixture.

$ df -h

Filesystem      Size  Used Avail Use% Mounted on
lab-root         20G  6.4G   14G  32% /
lab-logs        2.0G  180M  1.9G   9% /var/log

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Mount and capacity correlation”, which interpretation is safe?A device, partition, filesystem, and mount point are different concepts.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

Before adapting the lsblk workflow from “Mount and capacity correlation” to another server, what should you do?Paste the training paths unchanged into production.Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Scheduled service evidence Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual