⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 73 of 135 in Linux & SRE
Senior DevOps / SRE [L2] Linux Linux / SRE — Scenario-Based Interview Questions Production Scenario [L2]
🎯 Target Role / Context: Linux Scenario #31 (L2) · Linux / SRE — Scenario-Based Interview Questions

Q: A server's disks are incredibly slow. `iostat -x 1` shows %util at 100%. How do you identify whether it's latency on reading data or writing data?

While %util shows the disk is completely saturated (100% time spent doing I/O), it doesn't explain the load profile.

#Linux #L2 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: Deciphering complex I/O metrics, iostat columns.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: Deciphering complex I/O metrics, iostat columns.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

While %util shows the disk is completely saturated (100% time spent doing I/O), it doesn't explain the load profile.

  • r_await vs w_await: These denote the average wait time (in milliseconds) for Read requests vs Write requests to be served. If r_await is 5ms and w_await is 500ms, the disk is severely struggling to write.
  • rkB/s vs wkB/s: These denote the actual volume of Kilobytes Read vs Written per second.
2️⃣

Remediation & Permanent Safeguards

In the iostat output, I would focus on two specific column groups: If the write latency is massive, turning on Write-Back caching on a RAID controller, or migrating to an SSD, is the immediate hardware solution.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: r_await vs w_await: These denote the average wait time (in milliseconds) for Read requests vs Write requests to be served. If r_aw."
⚡ 60-Second Elevator Pitch Talking Points
  • r_await vs w_await: These denote the average wait time (in milliseconds) for Read requests vs Wri...
  • rkB/s vs wkB/s: These denote the actual volume of Kilobytes Read vs Written per second.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring servers disks incredibly SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
  2. Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring servers disks incredibly Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (df -h) shows ample free space.
  3. Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring servers disks incredibly Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
  4. Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring servers disks incredibly Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (pid_max).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →