ZFS no Storage

S

sb2014

Member
Feb 25, 2019
9
0
6
27
Good day,
Unfortunately, Proxmox gave the pool "rpool/ROOT/pve-1" only 1.5G disk space during installation.
Now the system does not start Proxmox anymore.
There is enough free space on the hard disks.
Anyone have an idea how to fix this?
Yours sincerely
sb2014

start errors:
chrome_I8W5TxEHdG.png

zfs list:
MobaXterm_ElvlVz96Ph.png
 
Hi,
it looks like vm-1500-disk-1 is using up all the space.
 
sb2014 ZFS is cool (and I love it) but you have to properly manage the storage quotes on your datasets and zvols. Fix the space vm-1500 is using, then set a reserved quota on rpool/ROOT of 32GB or something like that. Make sure you apply the reserved quota to apply to "this dataset and all of it's children"
 
Thank you for your answers.
vm-1500-disk-1 has only 25.6T of 30T allocated.
So there are still 4T over.
How exactly do I have to set this for rpool/ROOT.
I have already tried everything possible.
So far nothing has changed there.
 
ZFS uses thin provisioning and vm-1500-disk-1 is using all the space and the whole pool only got 1.25MB left. It doesn't matter if vm-1500-disk-1 is only using 25.6 of 30T. You also can give vm-1500-disk-1 1000T so its 25.6 of 1000T and your pool will be still full and stop working poperly when the pool runs out of space. With thin-provisioning you as the admin need to always monitor the pools free capacity and add more drives early enough so you never run out of free space. Also keep in mind that ZFS needs always around 10-20% of the space kept free for normal operation.
 
Last edited:
Add more drives to your pool to increase the total capacity or try to free up some space. I would look what data on that vm-1500-disk-1 isn't super important and can be deleted. Then delete it and make sure that discard is working so that ZFS receives TRIM commands to be able to free up that space. And like I said you want around 20% free space or your pool will get slow and start to fragment so deleting 5TB data of that vm-1500-disk-1 might be a good idea. Just problematic because I guess you can't start that VM if PVE can'T boot because the pool is full.
 
Last edited:
I would like to delete data.
Proxmox does not load because there is no disk space.
The VM does not start because proxmox does not load.
Is there any other way to access the content.
 
You could manually mount the zvol (like mounting a normal physical partition "/dev/sdx1" with the mount command but using the zvol instead which should be something like /dev/rpool/data/vm-1500-disk-1-partX) if you know what it was formated with so you can browse and delete stuff from your hosts CLI.
 
Last edited:
I have deleted data.
There are now 17T free on the VM 1500.
But ZFS says that there is still no space.
Snapshots don't seem to be there either.
What is the reason for this?

VM 1500:
MobaXterm_A18nW9EGZN.png

Host:
MobaXterm_oxs9aNNkgy.png
 
Did you do a fstrim -a or a zpool trim rpool so that deleted data actually gets freed up?
Also check if there are any snapshots blocking: zfs list -t snapshot rpool/data/vm-1500-disk-1
 
Last edited:
fstrim -a on the host or vm?
On the host: It does nothing.
On the vm: It has trimmed only 32 GB.

zpool trim rpool:
MobaXterm_RmNQKbTJrM.png
 
Do you have compression enabled on the volume (see here)?

Were the 32GB already reclaimed successfully? Then you could reserve more space for root as @Uplink suggested.
 
What do I do in such a case?
Does the whole thing work better with ext4 instead of zfs.
Or is the same problem there as well?

MobaXterm_kfmwgOCEG3.png
 
You must log in or register to reply here.
Top Bottom