Well, it does if you want to have all the copy-on-write benefits like snapshots. Sure, it does not add redundancy or extra performance (besides zfs great caching).
What are the quick and dirty steps (the ZFS commands) to create the pool, so that proxmox can use it to set up containers?
What are the quick and dirty steps (the ZFS commands) to create the pool, so that proxmox can use it to set up containers?
zpool create rpool /dev/sda4
zfs set compression=lz4 rpool
Back to the question:
Should be this:
Code:zpool create rpool /dev/sda4 zfs set compression=lz4 rpool
zfs is not a file-system. It is a storage manager. It can be used like a file-system and/or as block-device.
I had the partition on xfs before setting up the zfs pool. Does it matter what filesystem was on before creating the zfs pool? Does zfs overwrite the previous filesystem when creating the pool?
because zfs does not support ext4 style user quotasWhy was the "disk quota" option unavailable (dimmed) while setting up the CT on the zfs pool in the gui?