<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Storage Administration on MeerStory</title><link>https://linux.meerstory.com/categories/storage-administration/</link><description>Recent content in Storage Administration on MeerStory</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Oct 2026 01:29:06 +0900</lastBuildDate><atom:link href="https://linux.meerstory.com/categories/storage-administration/index.xml" rel="self" type="application/rss+xml"/><item><title>Mastering Linux blockdev: Query, Lock, and Tune Block Storage</title><link>https://linux.meerstory.com/ubuntu/20261014_012845_63/</link><pubDate>Wed, 14 Oct 2026 01:29:06 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261014_012845_63/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Effective disk management in Linux demands low-level control over drive parameters and kernel caching policies. The &lt;code>blockdev&lt;/code> command-line utility provides direct access to these block device ioctl interfaces. This walkthrough demonstrates how systems engineers inspect sector geometries, enforce read-only safety locks, and tune read-ahead buffers using an isolated virtual drive.&lt;/p>
&lt;h2 id="setting-up-an-isolated-loopback-device-for-safe-testing">Setting Up an Isolated Loopback Device for Safe Testing&lt;/h2>
&lt;p>Before applying low-level operations to live disks, spin up an isolated 100MB disk image by executing &lt;code>fallocate -l 100M /tmp/test_disk.img&lt;/code> in a temporary path.&lt;/p></description></item><item><title>Safely Teardown Linux Storage with blkdeactivate</title><link>https://linux.meerstory.com/ubuntu/20261013_022235_60/</link><pubDate>Tue, 13 Oct 2026 02:23:20 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261013_022235_60/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Decommissioning intertwined block devices—spanning active file system mounts, Device Mapper mappings, and Logical Volume Manager (LVM) structures—frequently introduces administrative friction and unmount errors. Rather than navigating theoretical manual pages, this practical walkthrough builds a sandboxed loopback and LVM testing environment from scratch, demonstrating how to gracefully disengage and tear down the entire storage stack using the &lt;code>blkdeactivate&lt;/code> utility.&lt;/p>
&lt;h2 id="1-setting-up-the-toolchain--exploring-blkdeactivate-syntax">1. Setting Up the Toolchain &amp;amp; Exploring blkdeactivate Syntax&lt;/h2>
&lt;p>Before orchestrating block-level deactivations, ensure the host system has the necessary device management packages by provisioning &lt;code>lvm2&lt;/code> and &lt;code>util-linux&lt;/code>.&lt;/p></description></item></channel></rss>