Search results

I don't think you answered my question but thanks. (See title: Any way around raw storage on container creation?) And as I said ZFS is the underlying filesystem...it's just over NFS. So, there is no security or performance benefit to raw images other than the quota? But I can set my own quotas...

I was wondering why Proxmox defaults to a raw rootfs when I create a new container. In fact, there seems to be no way around it. However, I really want to be able to directly access my files. They are on a nfs share backed by zfs so the raw image keeps me from using snapshot, rollback, clone...

I have a zpool with nested datasets: root@pve1:~# zfs list NAME USED AVAIL REFER MOUNTPOINT vault 1.50T 2.01T 1.50T /vault vault/files 52.8M 2.01T 96K /vault/files vault/files/apt-cache 52.6M 2.01T 52.6M...