VM shows half the disk space specified during creation
- Thread starter BNexus
- Start date
- To check disk capacity: # fdsik -l
- To check disk usage: # df -h
Proxmox Host:
2 x 1.2TB SAS, RAID 1
VM:
SCSI using local-lvm thin provisioning, default settings otherwise
I will note that I only started having this issue with I set up RAID 1 and reinstalled Proxmox. This install was markedly different from the last one, likely because I did this one manually from Proxmox ISO and the last one was a scripted install. There is a local disk of 100GB set up, and the rest of the space on the Proxmox host is local-lvm (LVM-thin). Last install, everything was kept on local.
Here is output of df -h and fdisk -l
Obviously I can expand my LV but is there a way to set it up to automatically use full available disk space? This isn't the only VM this occurs on.
2 x 1.2TB SAS, RAID 1
VM:
SCSI using local-lvm thin provisioning, default settings otherwise
I will note that I only started having this issue with I set up RAID 1 and reinstalled Proxmox. This install was markedly different from the last one, likely because I did this one manually from Proxmox ISO and the last one was a scripted install. There is a local disk of 100GB set up, and the rest of the space on the Proxmox host is local-lvm (LVM-thin). Last install, everything was kept on local.
Here is output of df -h and fdisk -l
Obviously I can expand my LV but is there a way to set it up to automatically use full available disk space? This isn't the only VM this occurs on.
Last edited:
We actually discovered that during Ubuntu install, the default part was only using half available space, which is new for both me and my client. We fixed it by resizing and I will note it for any future Ubuntu installs.
Thank you.
Just discovered the same. All my ubuntu server vms had half of the disk available. How bizarre.
I followed these steps to enlarge the volumes.
I followed these steps to enlarge the volumes.
Hello, noob here
The aim for my brand new proxmox is to run a few smallish dockers, such as jellyfin et-al. Learned the hard longwinded way that the praised PM containers cannot mount external NAS drives for use with data, only for it's internal use. Bummer.
Ok, so installed the much larger Ubuntu server 22.04 in the VM and things are running better and mounting of NAS data possible. However, I'm running out of space for the VM.
The created VM storage was created and reported to be 250GB. However, the actual space in the VM environment (df -h) is around 100GB.
I have tried resizing the VM disk but it does not change the result.
Is this a limitation in Proxmox, the OS or am I missing something? Suggestions of OS to run my dockers with? -I mainly have debian experience.
Thanks
The aim for my brand new proxmox is to run a few smallish dockers, such as jellyfin et-al. Learned the hard longwinded way that the praised PM containers cannot mount external NAS drives for use with data, only for it's internal use. Bummer.
Ok, so installed the much larger Ubuntu server 22.04 in the VM and things are running better and mounting of NAS data possible. However, I'm running out of space for the VM.
The created VM storage was created and reported to be 250GB. However, the actual space in the VM environment (df -h) is around 100GB.
I have tried resizing the VM disk but it does not change the result.
Is this a limitation in Proxmox, the OS or am I missing something? Suggestions of OS to run my dockers with? -I mainly have debian experience.
Thanks
They can. But only the less secure privileged LXCs and not the unprivileged ones. And those aren't great in case you plan to make your services public, like when wanting to access your jellyfin on the go without using a VPN. And running docker in a LXC is error-prone anyway.
Thats because you have chosen the standards when installing Ubuntu. By default the Ubuntu installer won't use the whole disk. You have to tell it when installing to make use of all the space.
And increasing the size of the virtual disk won't make your filesystem larger. Thats like replaying a physical 1TB with a 2TB disk and cloning its contents. The filesystem will still be 1TB wth 1TB unallocated.
You will have to manually extend the filesystem to make use of all the unallocated space. You maybe also have to extend the VG and LVs in case you are using LVM. Easiest probably would be to boot a gparted ISO in that VM and use it for extending your partitions, VGs, LVs and filesystems.
Ubuntu is a good choice. Debian will work too, but you might miss some docker features as Debian is always a bit behind.
Last edited:
As I prefer Debian over Ubuntu I tend to add their official repo: https://docs.docker.com/engine/install/debian/ - this way I have the best of both Debian and Docker...
(Btw: all of my (very few) Docker containers all locked into a separate VM each. One VM == one service.)
I've meant missing features like fewer storage drivers available when using Debian, because its kernel is usually behind and those then require a recent one.
Edit:
Looks like it is not a big problem now, but I remember needing to use "fuse-overlayfs" instead of "overlay2" when using rootless docker on some older Debians.
Edit:
Looks like it is not a big problem now, but I remember needing to use "fuse-overlayfs" instead of "overlay2" when using rootless docker on some older Debians.
Last edited: