Why is my VM running out of space

[Roysen]

I'm new to Proxmox so I'm pretty sure I made a mistake when setting up my VM. As my title say's, I'm running out of space on the root partition of my VM even if dedicated 2TB for my os.



Setup:
3-node Proxmox cluster (9.1.4)
No HA activated
VM istalled on a SMB mount (OldNas) 2TiB
VM ID=100
OS on ID is Ubuntu server 24.04

roysen@seafile-pve:~$ sudo df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 795M 79M 716M 10% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 98G 98G 0 100% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 2.0G 102M 1.7G 6% /boot
overlay 98G 98G 0 100% /var/lib/docker/rootfs/overlayfs/9b6d4b7752e4e1b087fb312780674f632370505ca74929fb251267d8495dab0a
tmpfs 795M 12K 795M 1% /run/user/1000

Notice that /dev/mapper/ubuntu-vg-ubuntu--lv is 100%. Why is that?
This is my fdisk output.

sudo fdisk -l
Disk /dev/sda: 1.95 TiB, 2147483648000 bytes, 4194304000 sectors
Disk model: QEMU HARDDISK
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3B552D70-EE69-4EDD-ADB3-E4E2A147B43B

Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 4198399 4194304 2G Linux filesystem
/dev/sda3 4198400 4194301951 4190103552 2T Linux filesystem


Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Parted printout:

(parted) print all
Model: QEMU QEMU HARDDISK (scsi)
Disk /dev/sda: 2147GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB bios_grub
2 2097kB 2150MB 2147MB ext4
3 2150MB 2147GB 2145GB


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 107GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 107GB 107GB ext4

So what kind of stupid newbie mistake have I done and what can I do to fix it?

 

[Roysen]

lsblk of my VM:

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 2T 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 2G 0 part /boot
└─sda3 8:3 0 2T 0 part
└─ubuntu--vg-ubuntu--lv 252:0 0 100G 0 lvm /

And my fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-IwI8fkT0AkS4qvE5mr8mgvtvfZRzERQzzFn7m5fSDti8GjAXT7mTwQckA4DN8GHg / ext4 defaults 0 1
# /boot was on /dev/sda2 during curtin installation
/dev/disk/by-uuid/9edaa479-bb5b-438e-b793-a56d7b5a8e9d /boot ext4 defaults 0 1

/swap.img none swap sw 0 0

 

[Impact]

Please use code blocks so the formatting is preserved. For LVM you want to use pvs and lvs too.
Your LV is only 100G and can be resized like this: https://forum.proxmox.com/threads/vm-is-not-showing-all-disk-space.166433/#post-772165
You should also enable discard for the virtual disk: https://gist.github.com/Impact123/3dbd7e0ddaf47c5539708a9cbcaab9e3#discard

 

[Roysen]

Thank you so much Impact. That fixed my problem. Like I said a newbie mistake