zfs xattr=sa

[flexyz]

Hi

I read on the zfs-discuss list, that "xattr=sa" could improve performance on Linux - is this the case for ZFS on Proxmox?

Thanks

 

[fabian]

yes, at least for non-zvol datasets (i.e., the files on the host and container volumes). but be aware that this is a ZFS-on-Linux only feature, so no sending datasets to OpenZFS/Solaris/FreeBSD/..

 

[flexyz]

Ok thanks, so I can enable it on my LXC and SAMBA folders? and leave it on for my ZVOL/KVM

 

[fabian]

zvols don't have an xattr property as there are no xattrs that could be stored

 

[flexyz]

alright, so I can enable it on my shares and LXC folders?

 

[fabian]

sure, if you don't need to import the pool on non Linux systems

 

[Rhinox]

How can I set xattr=sa at PVE-installation? As I see, xattr has "sa" value only for /data/subvols, but for /ROOT, /ROOT/pve-s and /data it has value "on"...

 

[fabian]

you cannot set it at installation time, but afterwards using 'zfs set'. most properties get inherited, so you can set it on rpool/data or rpool and it will apply to that and everything below.

 

[Rhinox]

But if I set those properties after installation, those changed xattr-types are used only for new writes, aren't they? That's too late...

 

[fabian]

But if I set those properties after installation, those changed xattr-types are used only for new writes, aren't they? That's too late...

yes, changed properties are only used for newly written files. but in case of xattr, after a default PVE install the root partition/dataset (which is the only one with actual stuff written) does not have a single file with an xattr set.. so just set it before you setup a samba/NFS server or create any containers (or whatever else you use xattrs for )