⚡ ~/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 89 of 135 in Linux & SRE
Senior DevOps / SRE [L2] Linux Linux / SRE — Scenario-Based Interview Questions Production Scenario [L2]
🎯 Target Role / Context: Linux Scenario #48 (L2) · Linux / SRE — Scenario-Based Interview Questions

Q: A production server is running out of disk space on the root partition, but the disk has unallocated space. The root partition uses LVM. How do you extend the root filesystem online without downtime?

LVM (Logical Volume Manager) allows dynamic volume resizing without unmounting or rebooting.

#Linux #L2 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: LVM management, online filesystem resize.. 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: "Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: LVM management, online filesystem resize.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

LVM (Logical Volume Manager) allows dynamic volume resizing without unmounting or rebooting.

  • Check available space in the volume group: vgdisplay shows free Physical Extents (PE) in the VG.
  • Extend the logical volume: lvextend -l +100%FREE /dev/mapper/rootvg-rootlv (uses all free space).
  • Resize the filesystem online:
  • For ext4: resize2fs /dev/mapper/rootvg-rootlv
2️⃣

Remediation & Permanent Safeguards

Steps to extend the root filesystem: If the Volume Group itself has no free space but the physical disk has unpartitioned space, first create a new partition (fdisk or parted), create a Physical Volume (pvcreate /dev/sdaX), extend the VG (vgextend rootvg /dev/sdaX), then proceed with lvextend.

  • For XFS: xfs_growfs /
  • Verify: df -h / should now show the extended size.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Check available space in the volume group: vgdisplay shows free Physical Extents (PE) in the VG.."
⚡ 60-Second Elevator Pitch Talking Points
  • Check available space in the volume group: vgdisplay shows free Physical Extents (PE) in the VG.
  • Extend the logical volume: lvextend -l +100%FREE /dev/mapper/rootvg-rootlv (uses all free space).
  • Resize the filesystem online:
⛔ 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 server running disk 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 server running disk 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 server running disk 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 server running disk 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 →