Why are Windows ACL settings for a subfolder sometimes not saved?
Applicable Products
QTS
Root Cause
This issue is sometimes caused by misconfiguration issues from QTS Advanced Folder Permissions and Windows ACL support. When Advanced Folder Permissions are enabled for a folder, QTS defines permissions for the subfolders. If Windows ACL support is enabled later, the existing QTS permissions are mapped to the Windows ACL. However, if the subfolder hasn't been previously accessed by Windows, any new ACL settings are not saved in the folder's extended attributes. If Advanced Folder Permissions are later disabled in QTS, the folder will lose both types of permissions.
Solution
To resolve this issue, QNAP recommends users set the subfolder permissions from Windows File Explorer immediately after enabling Windows ACL. This ensures that ACL permissions are permanently added to the folder's extended attributes. Additionally, QNAP doesn't recommend enabling both Advanced Folder Permissions and Windows ACL support on a subfolder at the same time.
Further Reading
- How do I set up shared folders and the permission on the NAS running QTS?
- Should I enable Advanced Folder Permissions or Windows ACL support?
- After I enabled advanced folder permissions on a shared folder in QTS, why can’t I open files in the folder that were created remotely via Samba or AFP, if I access the files via NFS?
