1 views collected around this technical thread.
This article explains how to handle MySQL disk‑space alerts by using the pt‑online‑schema‑change (pt‑osc) tool to selectively retain needed rows, migrate data to a temporary table, and drop the original table, thereby achieving fast, low‑impact data cleanup.
This guide explains how to diagnose and fix TiKV disk‑space problems by identifying oversized log files, redundant space‑placeholder files, and excessive RocksDB/Titan data, offering command‑line checks, configuration tweaks such as enabling log rotation, disabling reserve space, and tuning GC and Titan discardable‑ratio to restore balanced storage.
This article explains why disk space may not be freed after deleting large log files on a Linux server, describes the underlying file system mechanisms, and provides a step‑by‑step troubleshooting guide using /tmp cleanup and the lsof command to identify and kill lingering processes.
The article demonstrates that adding an explicit primary key to a MySQL InnoDB table can dramatically reduce its on‑disk size by eliminating the hidden clustered index, and explains how invisible primary keys can be used when schema changes are not possible.
This article explains how to safely run MySQL's CLONE INSTANCE command with the DATA DIRECTORY option on a replica that lacks enough disk space for both source and target data sets, offering step‑by‑step strategies, SQL examples, and a final recommendation.
This article describes a step‑by‑step procedure for safely dropping a massive MySQL history_str table—including creating a new table, renaming, using hard links, staged drops, and a truncate script—to avoid instance hangs, replication lag, and I/O pressure while freeing disk space.
This article walks through a real‑world TiDB/TiKV disk‑space alarm case, diagnosing why the GC worker got stuck, how TiCDC’s lingering changefeed caused outdated MVCC versions, and the step‑by‑step commands and monitoring tricks used to restore normal GC and reclaim storage.
Even when the `df` command shows a full disk, hidden deleted files held open by processes can consume space, and understanding this requires diving into Linux’s virtual file system architecture, including superblocks, inodes, file and dentry objects, as well as link types and file‑process interactions.
This guide explains how to use Linux commands such as df, du, find, and lsof to quickly locate directories, files, or deleted resources that are consuming disk space, and shows how to adjust reserved space with tune2fs to recover seemingly missing storage.
This article explains why MySQL 8.0 appears to lose about 1 GB of disk space when temporary tables are used, detailing the experiment, the role of TempTable, mmap allocation, and how performance_schema and procfs can be used to observe the process.
This article introduces pnpm, a fast and disk‑space‑efficient JavaScript package manager that improves on npm and Yarn, explains its core features such as speed, content‑addressable storage, monorepo support, and strict dependency management, and provides practical usage examples and security considerations.
The article explains why a Linux system may report a full disk even after deleting files, detailing how open file handles keep space occupied, and walks through the virtual file system architecture—including superblocks, inodes, file and dentry objects—while demonstrating diagnostic commands like df, du, lsof, and illustrating link types and file‑process interactions.
The article explains how directories consume inodes and filesystem blocks, how this consumption grows with many files or long filenames, and why the ls command can become sluggish, offering practical tips to mitigate the performance impact.
The article investigates a MySQL crash caused by binlog errors due to a full '/' partition, explains why the error leads to server abort, demonstrates reproducing the issue with large transactions, traces the problem to the my_write function in the source code, and offers mitigation strategies such as reducing transaction size or expanding the temporary directory space.
The article investigates a sudden /tmp disk‑space explosion in a Flask‑based file transfer service, analyzes the Werkzeug form‑parsing code that creates temporary files for uploads larger than 500 KB, demonstrates reproducible tests with inotify and Python scripts, and offers practical recommendations to prevent similar failures.
This article explains why retrieving a MySQL table's on‑disk size via INFORMATION_SCHEMA.TABLES is unreliable, describes the impact of storage engines and row formats, and shows how to obtain accurate sizes by querying INNODB_SYS_TABLESPACES, including considerations for compression and configuration settings.
This article explains why MySQL can exhaust disk space when implicit temporary tables grow too large, describes how memory limits and storage‑engine choices affect their creation, and provides practical configuration and query‑optimization techniques to avoid service interruptions.
A CentOS web server reports 100% disk usage despite du -sh /* showing far less space used, which is caused by Apache/Tomcat logs being cleared while the services are running, and the issue is resolved by restarting the services and properly cleaning old log files.
This article explains why deleted files can still occupy disk space on a Linux server, demonstrates how to identify them with lsof, and shows how configuring Filebeat’s close_older and force_close_files settings can automatically release the space.