Q: How do you persistently mount a new EBS/block volume so it survives reboots?
First, I verify the block device name (lsblk), format it (mkfs.ext4 /dev/nvmeXn1), and mount it temporarily to verify (mount /dev/nvmeXn1 /data).
/etc/fstab configuration, UUIDs vs device names.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
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: /etc/fstab configuration, UUIDs vs device names.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
First, I verify the block device name (lsblk), format it (mkfs.ext4 /dev/nvmeXn1), and mount it temporarily to verify (mount /dev/nvmeXn1 /data).
- Find the UUID:
blkid /dev/nvmeXn1 - Add an entry to
/etc/fstab: - Test the entry without rebooting:
umount /datathenmount -a. If no errors are thrown, the system will safely mount it on the next boot. (Thenofailoption ensures the server still boots if the volume is detached).
Remediation & Permanent Safeguards
To make it persistent: I should never use the device name (like /dev/nvmeXn1) in /etc/fstab because cloud providers do not guarantee device name ordering across reboots. Instead, I use the UUID. UUID=123-abc-456 /data ext4 defaults,nofail 0 2
- Find the UUID: blkid /dev/nvmeXn1
- Add an entry to /etc/fstab:
- Test the entry without rebooting: umount /data then mount -a. If no errors are thrown, the system...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring persistently mount EBS/block SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring persistently mount EBS/block
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. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring persistently mount EBS/block Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring persistently mount EBS/block
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).