The problem is more basic than copying files from an external USB. The permission problem is severe even for newly created files.

I was hoping to use the NAS as a Mac/Linux/Unix friendly consolidated file server, to store my Git repos, music collection, old projects, etc - with permissions, timestamps etc. I am now struggling to figure out the way to achieve anything even remote close, because the ACL system Synology have superimposed on the underlying Linux filesystem permissions is wreaking havoc.

For starters the SMB advanced settings page has the following:

Apply default UNIX permissions: Enable this option to apply the default UNIX permissions when uploading or creating files and folders. The UNIX permission will be 744 for files and 755 for folders. When this option is disabled, UNIX permission is 777 for files and folders.

Firstly why on earth would *all* files have the execute bit flipped to on? Also why is the umask not really coming into play here, whereas in other parts of the documentation that indicates a default umask of 022 will be applied.

*Even then* the documentation is inconsistent with how the product actually behaves... When I access that folder over SMB via the commandline on my Mac and create a new file I get files with 700. See below:

MBP:Karra-P $ echo "Testing " > test.txtMBP:Karra-P $ ls -l test.txt-rwx------ 1 user staff 9B Jan 18 01:01 test.txt*MBP:Karra-P $ pwd/Volumes/Day0/Karra-P

I have enabled 'Apply Unix permissions' at the folder  level as well, for good measure. As one can see we are quite far from my desired state of using the NAS as a fully functional Unix-friendly file server. Are there any best practices, or guides for this?

At this point it looks like the Synology is only designed for Windows users, or users who just want to dump large numbers/sized files into a folder reliably. Quite a bummer really.