Free space

[Alessandro 123]

I have the following:

# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               63G     0   63G   0% /dev
tmpfs              13G  1.1G   12G   9% /run
rpool/ROOT/pve-1  357G  3.1G  354G   1% /
tmpfs              63G   37M   63G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
tmpfs              63G     0   63G   0% /sys/fs/cgroup
rpool/ROOT        354G  128K  354G   1% /rpool/ROOT
rpool/data        354G  128K  354G   1% /rpool/data
/dev/fuse          30M   28K   30M   1% /etc/pve
tmpfs              13G     0   13G   0% /run/user/0

how much free space I have, currently, for new VMs ?354G
I'm asking this because there are some apparent inconsistencies from the GUI

 

[Zac8236]

I have the following:

# df -h
Filesystem        Size  Used Avail Use% Mounted on
udev               63G     0   63G   0% /dev
tmpfs              13G  1.1G   12G   9% /run
rpool/ROOT/pve-1  357G  3.1G  354G   1% /
tmpfs              63G   37M   63G   1% /dev/shm
tmpfs             5.0M     0  5.0M   0% /run/lock
tmpfs              63G     0   63G   0% /sys/fs/cgroup
rpool/ROOT        354G  128K  354G   1% /rpool/ROOT
rpool/data        354G  128K  354G   1% /rpool/data
/dev/fuse          30M   28K   30M   1% /etc/pve
tmpfs              13G     0   13G   0% /run/user/0

how much free space I have, currently, for new VMs ?354G
I'm asking this because there are some apparent inconsistencies from the GUI

If you look under the LVM storage on the GUI, that's where the VM data gets stored by default.


The Host summary just shows how much room is avalible for ISOs etc


To do it in ther terminal, use

vgs -o +lv_size,lv_name

and look for the logical volume data.


Hope this helps

 

[Alessandro 123]

I dont use lvm but zfs

 

[wolfgang]

Hi,

with ZFS you can't tell 100% how much space is free.
df use static block size to calculate the free space.
But ZFS has dynamic block size and so it is hard to tell.
The Raid Level also influence the block usage.
The GUI uses the zfs command to get the free space.

 

[Alessandro 123]

Thank you.
As far as I know, using the "root pool" is a very bad practise and I see that proxmox is mounting that:

# zfs list
NAME                       USED  AVAIL  REFER  MOUNTPOINT
rpool                      480G   353G   140K  /rpool

is it safe to unmount ? Why are you mounting that ?

 

[Knuuut]

A zpool is immediately mounted after creation per default. This is NOT bad practice, this is a feature of zfs.

 

[Alessandro 123]

Using the root pool is a bad practice and you can set that as no mount (-O canmount=off)
Having it mounted to /rpool could lead to some bad practise

In example if you want to send rpool somewhere, you can't do it safely because receiving a full filesystem stream destroys the one already in place on the remote server and renames the received one to that name, which is impossible with the root filesystem of a pool as that can't be destroyed

So, is it safe to unmount the rpool in PVE ?

 

[Knuuut]

Using the root pool is a bad practice and you can set that as no mount (-O canmount=off)

I'm aware of this. If you don't like it, feel free to change it.

 

[Alessandro 123]

I'm aware of this. If you don't like it, feel free to change it.

So:
- 1 don't say that "is NOT a bad pratcise" while it is.
- 2 i'm asking if is safe to change it on an existing pool

 

[alexskysilk]

Using the root pool is a bad practice and you can set that as no mount (-O canmount=off)

I think there may be a disconnect in terms. you dont mount a pool, you mount an extent (zvol or zfs file system). There is no conflict or problem using different/multiple extents on the same pool; your vm storage arent using your root volume.

is it safe to unmount ? Why are you mounting that ?

Its technically possible to mount a child zvol in a nested pool, but to what end? there is no harm to have the parent mounted...