<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Disk-Management on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/disk-management/</link>
    <description>Recent content in Disk-Management on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/disk-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux LVM Management: Blivet-GUI vs System Storage Manager vs LVM2 CLI</title>
      <link>https://www.pistack.xyz/posts/2026-05-25-linux-lvm-management-tools-blivet-gui-ssm-lvm2-cli-guide/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-25-linux-lvm-management-tools-blivet-gui-ssm-lvm2-cli-guide/</guid>
      <description>&lt;p&gt;Logical Volume Management (LVM) is the standard storage abstraction layer on most enterprise Linux distributions, enabling flexible volume resizing, snapshotting, and pooling across multiple physical disks. But managing LVM through raw command-line tools like &lt;code&gt;lvcreate&lt;/code&gt; and &lt;code&gt;vgextend&lt;/code&gt; can be error-prone, especially in production environments where a mistyped command can destroy data. Three distinct approaches to LVM management have emerged: the traditional &lt;strong&gt;LVM2 CLI&lt;/strong&gt; toolset, the graphical &lt;strong&gt;Blivet-GUI&lt;/strong&gt; interface, and the unified &lt;strong&gt;System Storage Manager (SSM)&lt;/strong&gt;. Each offers different tradeoffs between power, safety, and ease of use.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
