Thanks for replying, I only did the dnodesize on the dataset rpool/data not on the rpool itself. I even went back into the live chroot env and changed it back, but to no avail.
I am using legacy boot, not UEFI.
Thanks, John
After setting zfs set xattr=sa dnodesize=auto RPOOL/data ( I read that you shouldnt set this on the RPOOL, so im not sure if this problem is due to this)
I can not boot any longer. I get this:
Attempting Boot From Hard Drive (C:)
error: no such device "SOME HEX NUMBER"
error: unknown...
Well Bil, what a newbie I feel. After all these years..... just seems like something I've never whiteness, or that I've never even opened my eyes to such inappropriate well-seasoned Linux admin behavior :D
proxmox is on the latest version and using ZFS rpool for everything. Can someone at least say why this is the case when writing to disk within the VM. The VM's memory us used up to the size of the file written to disk. Once you reboot the machine or delete the file, the memory is returned...
Hello,
I'm seeing when I write a large file within a VM linux, I'm also filing up the VM systems memory.
This memory is released when I delete the file.
dd if=/dev/zero of=test1.img bs=512k count=1000000
Is this normal?
Cheers
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these...