Filesystem Watcher Errors on Synology Subfolder

Support
7

Hi Simon:

Thanks for chipping in. It looks like getfacl isn’t included on Synology - but they have a synoacltool instead.

Here’s the output from the ‘broken’ folder:

# synoacltool -get /volume1/FolderName/SubfolderName/
ACL version: 1 
Archive: is_inherit,is_support_ACL 
Owner: [sc-syncthing(user)] 
--------------------- 
	 [0] user:adam:deny:rwxpdDaARWcCo:fd--  (level:1)
	 [1] group:administrators:allow:rwxpdDaARWc--:fd--  (level:1)
	 [2] group:workshop:allow:rwxpdDaARWc--:fd--  (level:1)
	 [3] group:office:allow:rwxpdDaARWc--:fd--  (level:1)
	 [4] group:sc-syncthing:allow:rwxpdDaARWc--:fd--  (level:1)
	 [5] group:machines:allow:rwxpdDaARWc--:fd--  (level:1)

And the output from a neighbouring working folder:

# synoacltool -get /volume1/FolderName/Subfolder2Name/
ACL version: 1 
Archive: is_inherit,is_support_ACL 
Owner: (user) not found 
--------------------- 
	 [0] user:adam:deny:rwxpdDaARWcCo:fd--  (level:1)
	 [1] group:administrators:allow:rwxpdDaARWc--:fd--  (level:1)
	 [2] group:workshop:allow:rwxpdDaARWc--:fd--  (level:1)
	 [3] group:office:allow:rwxpdDaARWc--:fd--  (level:1)
	 [4] group:sc-syncthing:allow:rwxpdDaARWc--:fd--  (level:1)
	 [5] group:machines:allow:rwxpdDaARWc--:fd--  (level:1)

The only difference I can see is the owner of the ‘broken’ subfolder is the sc-syncthing user - but, as I say, there are other neighbouring folders which have the same owner, and they’re not reporting a problem…