Back to the map

Module 07 · File systems and I/O · Drill

File systems and I/O drill

Scenario prompts that check whether file systems and i/o is usable under pressure. Answer out loud, then compare.

4 prompts25 minNew

0 of 4 graded

  1. Prompt 1

    You are building a small embedded job queue that persists jobs to a local file so they survive crashes and power loss. Specify exactly how you append jobs, when you acknowledge them to producers, and how you recover, and estimate throughput if each fsync takes 0.5 ms.

    Say your answer out loud first. Thirty seconds is enough.
  2. Prompt 2

    A logging agent on each host writes application logs to /var/log and rotates them nightly. Last week several hosts filled their disks: df showed 100 percent, but du over /var/log summed to only 20 GB of a 100 GB disk. A different host failed with 'No space left on device' while df showed 35 percent free. Diagnose both incidents and prevent them.

    Say your answer out loud first. Thirty seconds is enough.
  3. Prompt 3

    A nightly backup job on the same NVMe-backed database host makes the database's p99 write latency jump from 2 ms to 40 ms for two hours. The backup reads the data directory with a single-threaded file copy. Explain what competes, how you would measure it, and three fixes.

    Say your answer out loud first. Thirty seconds is enough.
  4. Prompt 4

    A static-file and video-segment server on Linux serves 20 Gbit/s and is CPU-bound, with profiles showing time in copying and in read and write system calls. Explain where the copies and system calls come from and redesign the serving path.

    Say your answer out loud first. Thirty seconds is enough.
File systems and I/O drill · Backplane