From fc79f358eb6a1dd7ed2e5f5b1e31fb664a182595 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Mon, 30 Aug 2010 10:45:52 +0200 Subject: docs-xml/vfs_gpfs: document 'gpfs:refuse_dacl_protected' metze --- docs-xml/manpages-3/vfs_gpfs.8.xml | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) (limited to 'docs-xml/manpages-3/vfs_gpfs.8.xml') diff --git a/docs-xml/manpages-3/vfs_gpfs.8.xml b/docs-xml/manpages-3/vfs_gpfs.8.xml index 4963ecd88a..6421fc6796 100644 --- a/docs-xml/manpages-3/vfs_gpfs.8.xml +++ b/docs-xml/manpages-3/vfs_gpfs.8.xml @@ -169,6 +169,37 @@ + gpfs:refuse_dacl_protected = [ yes | no ] + + + As GPFS does not support the ACE4_FLAG_NO_PROPAGATE NFSv4 flag (which would be + the mapping for the DESC_DACL_PROTECTED flag), the status of this flag is + currently silently ignored by Samba. That means that if you deselect the "Allow + inheritable permissions..." checkbox in Windows' ACL dialog and then apply the + ACL, the flag will be back immediately. + + + To make sure that automatic migration with e.g. robocopy does not lead to + ACLs silently (and unintentionally) changed, you can set + gpfs:refuse_dacl_protected = yes to enable an explicit + check for this flag and if set, it will return NT_STATUS_NOT_SUPPORTED so + errors are shown up on the Windows side and the Administrator is aware of + the ACLs not being settable like intended + + + + + no(default) - ignore the DESC_DACL_PROTECTED flags. + + + yes - reject ACLs with DESC_DACL_PROTECTED. + + + + + + + nfs4:mode = [ simple | special ] -- cgit