This article explains Linux filesystem structures, the virtual filesystem layer, various disk I/O mechanisms—including buffered, non‑buffered, blocking, non‑blocking, synchronous and asynchronous I/O—and provides practical commands for observing inode and dentry caches to aid performance optimization.
This article explores Linux file system fundamentals, covering physical disk layout, partition strategies, how the OS reduces random‑read latency, the real space cost of empty files and directories, inode usage, block allocation, and practical tips for improving disk I/O performance.
This article explains the physical structure of mechanical disks, partitioning strategies, inode and block allocation, and how filename length and directory layout affect Linux file system performance, providing practical experiments and tips for improving disk I/O.
This article explains what inodes are, why they can become exhausted despite available disk space, and provides practical Linux commands and preventive steps to identify and resolve inode exhaustion issues.
The article explains what inodes are, why they can become fully consumed even when disk space remains, and provides step‑by‑step Linux commands and cron adjustments to identify the offending directories, delete excess files, and prevent future inode exhaustion.
The article explains what inodes are, why they can become fully consumed even when disk space remains, how to monitor inode usage with df -i, and provides practical steps and command‑line scripts to locate offending directories, delete excess files, and prevent future inode exhaustion on Linux systems.
This article explains how Linux models all resources—including disks, devices, and inter‑process communication—as files, describes the physical storage mechanisms of hard drives, and walks through the steps of partitioning, formatting, mounting, and navigating the Linux file system hierarchy.
A MySQL fatal error claiming "Can't create/write to file ... (Errcode: 28)" turned out not to be a lack of disk space but exhausted inodes caused by millions of tiny maildrop files generated by cron‑driven Postfix notifications, and the article walks through the investigation and fix.
A MySQL fatal error citing Errcode 28 can stem from inode exhaustion caused by a flood of cron-generated emails, not just lack of disk space, and the article walks through diagnosing the issue with df, df -i, and locating the offending Postfix maildrop directory.
This article explains the Unix principle that everything is a file, describes regular and special file types, outlines why and how disks are partitioned, introduces mount points, and details the standard Linux filesystem hierarchy and inode metadata.
