<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Disk Resize on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/disk-resize/</link>
    <description>Recent content in Disk Resize on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 23 Mar 2026 10:30:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/disk-resize/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resize the disk of an Ubuntu VM in PVE — the complete workflow from Web UI to guest OS</title>
      <link>https://blog.margrop.net/en/post/pve-ubuntu-vm-disk-resize/</link>
      <pubDate>Mon, 23 Mar 2026 10:30:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/pve-ubuntu-vm-disk-resize/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Preface&lt;/strong&gt;&#xA;When you manage a virtualized environment with Proxmox VE, running out of disk space is only a matter of time. Maybe your Ubuntu VM keeps pulling more Docker images, or maybe database logs fill up the root partition. In short, disk expansion is a must-have skill for PVE operations. This article walks through the entire process, from resizing the virtual disk in the PVE Web UI to expanding LVM inside the Ubuntu guest, step by step.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;1-why-do-we-need-to-resize&#34;&gt;1 Why do we need to resize?&lt;/h2&gt;&#xA;&lt;p&gt;PVE usually allocates a fixed-size virtual disk when a VM is created, for example 32 GB. As the workload grows, that space may no longer be enough. Fortunately, PVE supports online disk expansion, and Ubuntu&amp;rsquo;s default LVM setup also supports dynamic logical volume expansion. Together, they make the process very convenient.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
