Extending an LVM volume: Physical volumes (partitions) -> Volume groups -> Logical volume -> Filesystem

Thanks.  I agree that having one partition for TurnKey makes the most sense as a default.

I'll definitely get around to trying EC2 so I can get a feel for things.  I especially need to figure out how easy it is to add space to the EC2 instance's root partition.

Hi,

I know this is an old post but I inherited Turnkey and root is out if disk space and mysql will not load. I followed your article and it worked: but still 0% available, I think I am overlooking something simple. Any ideas? Thanks.

root@aserver~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/turnkey-root
                       22G   21G     0 100% /
none                  120M  184K  120M   1% /dev
none                  123M     0  123M   0% /dev/shm
none                  123M   56K  123M   1% /var/run
none                  123M     0  123M   0% /var/lock
none                  123M     0  123M   0% /lib/init/rw
/dev/sda1             473M  437M   12M  98% /boot

>

root@aserver ~# fdisk -l

Disk /dev/sda: 53.7 GB, 53687091200 bytes
4 heads, 32 sectors/track, 819200 cylinders
Units = cylinders of 128 * 512 = 65536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000339d8

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        7813      500000   83  Linux
/dev/sda2            7825      305168    19030016   8e  Linux LVM
/dev/sda3          305169      573440    17169408   83  Linux
/dev/sda4          573441      819200    15728640   83  Linux

Disk /dev/sdb: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table
root@aserver ~# ls /dev/sd*
/dev/sda  /dev/sda1  /dev/sda2  /dev/sda3  /dev/sda4  /dev/sdb
root@aserver ~# pvcreate /dev/sda4
  Physical volume "/dev/sda4" successfully created
root@aserver ~# vgextend turnkey /dev/sda4
  Volume group "turnkey" successfully extended
root@aserver ~# lvextend -L+15 /dev/turnkey/root
  Extending logical volume root to 37.02 GiB
  Logical volume root successfully resized
root@aserver ~# resize
resize2fs   resizecons
root@aserver ~# resize2fs /dev/turnkey/root
resize2fs 1.41.11 (14-Mar-2010)
Filesystem at /dev/turnkey/root is mounted on /; on-line resizing required
old desc_blocks = 2, new_desc_blocks = 2
Performing an on-line resize of /dev/turnkey/root to 5771264 (4k) blocks.
The filesystem on /dev/turnkey/root is now 5771264 blocks long.

>

root@aserver~# vgdisplay
  --- Volume group ---
  VG Name               turnkey
  System ID
  Format                lvm2
  Metadata Areas        4
  Metadata Sequence No  15
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               2
  Max PV                0
  Cur PV                4
  Act PV                4
  VG Size               57.51 GiB
  PE Size               4.00 MiB
  Total PE              14722
  Alloc PE / Size       10116 / 39.52 GiB
  Free  PE / Size       4606 / 17.99 GiB
  VG UUID               xDapZk-53wD-mIKE-5OZQ-zd3M-EggS-enn5xC

 

But I have heard some good things about it. I personally use ProxmoxVE and find it really good. TKL installs to KVM no worries (from ISO) and I have also converted lots of images to run under OVZ (PVE has both). Theoretically the TKL VM images should be able to be imported into KVM but I have only played with it once and dind't have any joy (I didn't try real hard because it's pretty quick and easy to install from ISO). But I agree a KVM image that could be easily imprted would be a plus.

dd is pretty slow but I have successfully dd'd up to 250GB images over a network (SHH) successfully on a number of occasions. That's how I migrated my physical Win2K3 server to a KVM VM. I just used a live CD and dd'd the HDD to a .raw image and KVM picked that up fine. But as I say that was with PVE not Eucalyptus so obviously YMMV.

That's a whole other issue then. My advice to start with would be to take an image of the drive before doing anything. Ideally I like to image to a same or larger size drive. dd is the go, or ddrescue if there are hardware or data corruption issues.

Otherwise I'm not much help. I had a HDD fail on me some time ago and I managed to recover some of the data (about a quarter) by writing a new super block, but I don't recall how I did it... Sorry...

I missed your post here. FWIW unless it's a really recent blog post, to ensure timely response, you are probably best to start a new thread in the forums.

Anyway, as a general rule, we highly recommend using TKLBAM for backups. WOrst case you could have then restored the data to a new VM (with a bigger root volume) off the bat. Obviously a snapshot would also work. And all of that is moot now anyway...

FWIW log files are usually only pretty small so unlikely cleaning up them will give you enough room. Probably the best way to clear a bit of space is removing the apt cache:

apt-get clean

Although obviously how much room that will give you will depend on how much stuff is there (and when/if you've ever run it before).

One really handy tool to see what is taking up all your space (and give you ideas for removal candidates) is ncdu. It's not that big, but obviously it's preferable to install it before lack of space becomes an issue... Install that like this:

apt-get update && apt-get install ncdu

Then to look at your whole system, launch it like this:

ncdu /

It will show you all the files and directories in / ordered by size.

As a general rule, keeping a regular eye on your free space before it becomes a problem is highly recommended. Again probably not much use to you this time, but hopefully might help save headaches next time!? :)

When you add the new disk, don't partition it at all. You don't even want a partition table. I know that sounds weird, but that's what you'll need to do.

I've just had a closer look at my home server because I was sure that I had a VG larger than 2TB. It's not TurnKey, but it is Debian Jessie based (same as TurnKey) so I was hoping it should be the same. Unfortunately, it seems that the version of LVM I have is a little newer, so YMMV.

root@tkl-14-2 ~# lvm version
  LVM version:     2.02.111(2) (2014-09-01)
  Library version: 1.02.90 (2014-09-01)
  Driver version:  4.27.0

root@pve ~# lvm version
  LVM version:     2.02.116(2) (2015-01-30)
  Library version: 1.02.93 (2015-01-30)
  Driver version:  4.34.0

Unfortunately, the different lvm version means I can't be sure this will work for you (but hopefully it will). It turns out that I do have a VG over 2TB, but only just. FWIW, here's how it looks:

root@pve ~# vgdisplay pve3
  --- Volume group ---
  VG Name               pve3
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  3
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               2.73 TiB
  PE Size               4.00 MiB
  Total PE              715396
  Alloc PE / Size       707789 / 2.70 TiB
  Free  PE / Size       7607 / 29.71 GiB
  VG UUID               eMT1kU-T5ZC-9HzC-QgpG-5Mmb-tqOj-ZK7ESO

And it's just a single disk (3TB on the cover; ~2.7TB in the real world):

root@pve ~# pvdisplay /dev/sdb
  --- Physical volume ---
  PV Name               /dev/sdb
  VG Name               pve3
  PV Size               2.73 TiB / not usable 4.46 MiB
  Allocatable           yes 
  PE Size               4.00 MiB
  Total PE              715396
  Free PE               7607
  Allocated PE          707789
  PV UUID               hAv4dj-yTXL-Cikh-lgpr-EcUs-DDbb-ZaU20r

And it's not partitioned at all:

root@pve ~# fdisk -l /dev/sdb

Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

So give that a go, hopefully that will work for you.

If that still doesn't work, perhaps one more thing worth trying is to create individual partitions smaller than 2TB and add them all to the same VG. TBH, I'm not sure it will work, but hopefully...

Hi Jeremy,
Thanks again for your help. Here is the output:

root@lamp ~# resize2fs 
/dev/turnkey/root resize2fs 1.43.4 (31-Jan-2017) The filesystem is already 25144320 (4k) blocks long. Nothing to do! 

root@lamp ~# df -h 
Filesystem                Size  Used Avail Use% Mounted on
udev                      4.9G     0  4.9G   0% /dev
tmpfs                    1001M   13M  988M   2% /run
/dev/mapper/turnkey-root   95G   12G   79G  14% /
tmpfs                     4.9G     0  4.9G   0% /dev/shm
tmpfs                     5.0M     0  5.0M   0% /run/lock
tmpfs                     4.9G     0  4.9G   0% /sys/fs/cgroup

root@lamp ~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=5109612k,nr_inodes=1277403,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1024312k,mode=755)
/dev/mapper/turnkey-root on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=42,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9804)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)

root@lamp ~# cat /etc/fstab
/dev/mapper/turnkey-root        /       ext4    errors=remount-ro       0       1
/dev/mapper/turnkey-swap_1      none    swap    sw      0       0

root@lamp ~# pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda1
  VG Name               turnkey
  PV Size               18.57 GiB / not usable 608.50 KiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              4753
  Free PE               0
  Allocated PE          4753
  PV UUID               EHxRup-p9EQ-hXeO-Sd6g-suT5-uLwG-QT4p1z

  --- Physical volume ---
  PV Name               /dev/sda2
  VG Name               turnkey
  PV Size               77.85 GiB / not usable 1.52 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              19930
  Free PE               0
  Allocated PE          19930
  PV UUID               k44hv7-TtkM-yPND-eRR7-enZN-7PVE-Xi92Xl

root@lamp ~# vgdisplay
  --- Volume group ---
  VG Name               turnkey
  System ID
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  12
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               96.42 GiB
  PE Size               4.00 MiB
  Total PE              24683
  Alloc PE / Size       24683 / 96.42 GiB
  Free  PE / Size       0 / 0
  VG UUID               i36ljm-rI3j-LNIe-eYPs-AYEb-w8ca-ddtCyN

root@lamp ~# lvdisplay
  --- Logical volume ---
  LV Path                /dev/turnkey/root
  LV Name                root
  VG Name                turnkey
  LV UUID                Hzcyyq-iTnJ-Y6Fl-igdZ-bO3a-vg1n-KKLj64
  LV Write Access        read/write
  LV Creation host, time tkldev, 2018-11-28 19:39:19 +0000
  LV Status              available
  # open                 1
  LV Size                95.92 GiB
  Current LE             24555
  Segments               3
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

  --- Logical volume ---
  LV Path                /dev/turnkey/swap_1
  LV Name                swap_1
  VG Name                turnkey
  LV UUID                RmerUk-Kt62-eZ2M-6t5L-Gfik-vllg-K32ueP
  LV Write Access        read/write
  LV Creation host, time tkldev, 2018-11-28 19:39:19 +0000
  LV Status              available
  # open                 2
  LV Size                512.00 MiB
  Current LE             128
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1

root@lamp ~# growpart /dev/sda 1
NOCHANGE: partition 1 could only be grown by 1051 [fudge=2048]