dst crerate chmod: operation not permitted on FreeNAS

[ghost]

v0.12.16, FreeBSD (64 bit) (Actually FreeNAS 9.3)

I've got two folders that are failing to finish syncing, but the one that I actually get log files from is as follows:

For anyone else wondering, you need to change the "command_args" line to read

command_args="-p ${pidfile} ${procname} -home=${syncthing_dir} -no-browser ${syncthing_args} > ${syncthing_dir}/syncthing.log"
before you get any logs at all.

[VQDC7] 19:59:44 INFO: Puller (folder "Books", file "9781921134333.pdf"): dst create chmod: chmod /mnt/sync/Books/.syncthing.9781921134333.pdf.tmp: operation not permitted
[VQDC7] 19:59:44 INFO: Puller: final: chmod /mnt/sync/Books/.syncthing.9781921134333.pdf.tmp: operation not permitted
[VQDC7] 19:59:44 INFO: Puller (folder "Books", file "9781921134876.epub"): dst create chmod: chmod /mnt/sync/Books/.syncthing.9781921134876.epub.tmp: operation not permitted
[VQDC7] 19:59:44 INFO: Puller: final: chmod /mnt/sync/Books/.syncthing.9781921134876.epub.tmp: operation not permitted

I know this is a permissions issue and not really syncthing's problem, but perhaps there could be more info in the UI? Especially for FreeNAS where the plugin designers have decided that users don't need logs at all.

root@syncthing_1:/mnt/sync/Books # ls -lah
total 47195
drwxrwxr-x+ 2 syncthing  syncstorage     5B Jan 24 18:42 .
drwxrwxr-x+ 6 1001       syncstorage     6B Jan 24 18:41 ..
-rwxrwxr-x+ 1 syncthing  syncstorage     0B Jan 24 18:41 .stfolder
-rwxrwxr-x+ 1 syncthing  syncstorage    17M Jan 24 18:42 .syncthing.9781921134333.pdf.tmp
-rwxrwxr-x+ 1 syncthing  syncstorage    28M Jan 24 18:42 .syncthing.9781921134876.epub.tmp

(I actually have a second folder that I suspect has similar problems, but it's got to ~20% synced and I can't see any log entries)

[ghost]

Could be related to https://forums.freenas.org/index.php?threads/cant-chmod-files-operation-not-permitted.22229/#post-131671 but that's just insanity. I'm not even sure how you'd work around it.

[ghost]

Yep, just created a new dataset with Unix-only permissions and it worked fine.