A mail server keeps filling its root filesystem because spooled mail and logs grow without bound, and when the disk fills the whole system becomes unusable. Which single change to the disk layout most directly contains that failure?
LPIC-1 Exam 101-500, objective 102. Linux installation and package management medium
Draft — not checked yet. This question was written from the published exam objectives and cites the clause it comes from, but nobody has yet read it against that clause and signed for it.
It is kept out of search results and out of mock exams until they have. Read the source below before you take the answer as settled.
The options
Not correct Put /boot on its own filesystem
Wrong. A separate /boot exists so the boot loader can reach kernels and initramfs images on a simple filesystem; it is small, nearly static, and absorbs none of this growth.
Not correct Put /home on its own filesystem
Wrong for this workload. Separating /home protects user data across reinstalls and limits user-created growth, but the mail spool and logs are not under /home, so the root filesystem still fills.
Correct Put /var on its own filesystem
Correct. Mail spools (/var/spool/mail or /var/mail) and logs (/var/log) both live under /var, so giving /var its own filesystem means runaway growth fills only that filesystem and leaves the root filesystem writable.
Not correct Increase the size of the swap area
Wrong. Swap is backing store for memory pages and is not part of any filesystem's free space. Growing it does not give the mail spool or logs anywhere else to go.
Why
The point of splitting mount points is fault isolation: data that grows unpredictably should not share a filesystem with the data the system needs to keep functioning. Variable data — logs, mail spools, print queues, package caches, databases — lives under /var, so /var is the classic separate filesystem on a server. Also note that giving each of these areas its own filesystem is a tradeoff: space stranded in one filesystem cannot be borrowed by another unless the volumes are managed by LVM.
Where this comes from
- Cited
- LPI exam objective 102.1
- What it says
- Design a disk partitioning scheme, allocating filesystems and swap space to separate partitions or disks.
Practise this
Reading one question is not practice. The trainer will draw a set from objective 102 and space the ones you get wrong.