Recent content by haroldas194

Actually, a bit of a brainfart. As you use ZFS, you don't use EXT4 at all. So naturally you won't have the issue with reserved space, which isn't a thing in ZFS same as it is in EXT4. This would only affect any storage system where the underlying FS is EXT4, like in my tests LVM-Thin+EXT4.

Interesting. So there might be a difference in how Proxmox handles it with ZFS (which I see you use) vs LVM. I just did the same test as you did but I use LVM. New CT, default 5% reserved root@pve:~# tune2fs -l /dev/mapper/data--ssd-vm--107--disk--0 | awk -F: '/Block count:/ {gsub(/^[ \t]+/, ""...

When creating a container by default it creates a FS with 5% EXT4 reserved space, e.g. tune2fs -l /dev/mapper/data--ssd-vm--999--disk--0 | awk -F: '/Block count:/ {gsub(/^[ \t]+/, "", $2); total=$2} /Reserved block count:/ {gsub(/^[ \t]+/, "", $2); res=$2} END {printf "Reserved: %.2f%%\n"...

Could anybody share any insights as to why this is happening? At first I thought due to not enough space, yet snapshots doesn't take any space whe not modifed and I am able to create them normally. vzdump 100 101 --mailto REDACTED@REDACTED.COM --node REDACTED --mode PBS --storage backup --quiet...

A bit info about setup: I ordered second IP for my server and I would like to use it to provider internet connectivity to my VMs in NAT Config: auto lo iface lo inet loopback iface lo inet6 loopback auto enp3s0 iface enp3s0 inet static address MAIN IP/32 gateway MAIN IP GW...