From 65aafb14b7bb0f928d6e076602c2c1d11e11b3dd Mon Sep 17 00:00:00 2001 From: Uri Simchoni Date: Fri, 3 Mar 2017 22:00:00 +0200 Subject: [PATCH] doc: update "ea support" section of the smb.conf manpage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This section was badly outdated. Signed-off-by: Uri Simchoni Reviewed-by: Ralph Boehme Autobuild-User(master): Ralph Böhme Autobuild-Date(master): Sun Mar 12 21:04:11 CET 2017 on sn-devel-144 --- docs-xml/smbdotconf/protocol/easupport.xml | 27 +++++++++++++++++----- 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/docs-xml/smbdotconf/protocol/easupport.xml b/docs-xml/smbdotconf/protocol/easupport.xml index 4c98267e5da..b453b86d78a 100644 --- a/docs-xml/smbdotconf/protocol/easupport.xml +++ b/docs-xml/smbdotconf/protocol/easupport.xml @@ -4,12 +4,27 @@ xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> This boolean parameter controls whether smbd - 8 will allow clients to attempt to store OS/2 style Extended - attributes on a share. In order to enable this parameter the underlying filesystem exported by - the share must support extended attributes (such as provided on XFS and EXT3 on Linux, with the - correct kernel patches). On Linux the filesystem must have been mounted with the mount - option user_xattr in order for extended attributes to work, also - extended attributes must be compiled into the Linux kernel. + 8 will allow clients to attempt to access extended + attributes on a share. In order to enable this parameter on a setup with default VFS modules: + + + Samba must have been built with extended attributes support. + + The underlying filesystem exposed by the share must support extended + attributes (e.g. the getfattr1 / setfattr1 + utilities must work). + + + + Note that the SMB protocol allows setting attributes whose value is 64K bytes long, + and that on NTFS, the maximum storage space for extended attributes per file is 64K. + On most UNIX systems (Solaris and ZFS file system being the exception), the limits + are much lower - typically 4K. Worse, the same 4K space is often used to store + system metadata such as POSIX ACLs, or Samba's NT ACLs. Giving clients + access to this tight space via extended attribute support could consume all + of it by unsuspecting client applications, which would prevent changing + system metadata due to lack of space. + no