Q: The OS memory is exhausted, but `top` and `ps` show that the sum of all running applications is only using 20% of the RAM. You clear the page cache, but the memory is still gone. Where is the "missing" memory?
If user-space processes and the page cache aren't holding the memory, it is allocated directly within the Kernel Slab Allocator.
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: Kernel Slab allocations, dentry/inode caches, memory leaks in kernel modules.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
If user-space processes and the page cache aren't holding the memory, it is allocated directly within the Kernel Slab Allocator. The Slab holds kernel structures like active dentry caches (directory paths) or inodes, or it's a literal memory leak caused by a buggy kernel driver. I would run the slabtop command. If slabtop shows the dentry cache is gigabytes in size, the server has traversed millions of tiny files recently. While normally the system reclaims this under pressure, sometimes a sysctl vm.drop_caches=3 is required to force the kernel to let go of directory structures, immediately restoring the "missing" memory.
- Immediate Triage: If user-space processes and the page cache aren't holding the memory, it is allocated directly
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
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 memory exhausted show 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 memory exhausted show
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 memory exhausted show 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 memory exhausted show
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).