From 02d0daafdbf31c537b39ab544cbab5690c81c4d0 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Tue, 15 Mar 2022 10:21:04 -0500 Subject: [PATCH] clarify that the script assumes MBR --- .../index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/posts/2021/automatic-unattended-expansion-of-linux-root-lvm-volume-to-fill-disk/index.md b/content/posts/2021/automatic-unattended-expansion-of-linux-root-lvm-volume-to-fill-disk/index.md index 850b8ae..0d6da83 100644 --- a/content/posts/2021/automatic-unattended-expansion-of-linux-root-lvm-volume-to-fill-disk/index.md +++ b/content/posts/2021/automatic-unattended-expansion-of-linux-root-lvm-volume-to-fill-disk/index.md @@ -25,6 +25,10 @@ It was a bit trickier for Linux systems though. My Linux templates all use LVM t I found a great script [here](https://github.com/alpacacode/Homebrewn-Scripts/blob/master/linux-scripts/partresize.sh) that helped with most of those operations, but it required the user to specify the physical and logical volumes. I modified it to auto-detect those, and here's what I came up with: +{{% notice info "MBR only" %}} +When I cobbled together this script I was primarily targeting the Enterprise Linux (RHEL, CentOS) systems that I work with in my environment, and those happened to have MBR partition tables. This script would need to be modified a bit to work with GPT partitions like you might find on Ubuntu. +{{% /notice %}} + ```shell #!/bin/bash # This will attempt to automatically detect the LVM logical volume where / is mounted and then