January 2, 20251 yr I seem to randomly get this error when writing files to the array. As far as I can tell there is no problem with the file itself, it writes correctly and reads correctly but im curious if anyone has seen this before. Googling around hasn't helped much. I am writing to a cache drive, i've never seen this when mover invokes. I tried Tools-> repair permissions but I still sporadically get the error. I'm on 6.12.14. Quote Jan 1 21:40:44 nas smbd[29716]: smbd_calculate_maximum_allowed_access_fsp: Could not get acl on file movies/movie4transcode.mp4: NT_STATUS_ACCESS_DENIED It seems the new file permissions are the username of my SMB account, shouldn't they be 'nobody'? Quote root@nas:/mnt/user/stuff# ls -l "movies/movie4transcode.mp" -rwxrw-rw- 1 smbusername users 379485 Jan 1 21:40 movies/movie4transcode.mp EDIT: I don't think the above is the issue, it seems all new files I write are using my smb username. Still not sure where this error is coming from since it's sporadic. Edited January 2, 20251 yr by oliver
January 3, 20251 yr Community Expert On 1/2/2025 at 4:25 AM, oliver said: I seem to randomly get this error when writing files to the array. As far as I can tell there is no problem with the file itself, it writes correctly and reads correctly but im curious if anyone has seen this before. Googling around hasn't helped much. I am writing to a cache drive, i've never seen this when mover invokes. I tried Tools-> repair permissions but I still sporadically get the error. I'm on 6.12.14. It seems the new file permissions are the username of my SMB account, shouldn't they be 'nobody'? EDIT: I don't think the above is the issue, it seems all new files I write are using my smb username. Still not sure where this error is coming from since it's sporadic. This looks like a fodler share that a docker has file access and has a different acl lock whille using the file. due to same paths being used... you may need to edit the samba config and set the write user/group.... force user=nobody force group=users ^- this is a per share samba option... array stoped - settings - samba/smb - smb extra options and or occasionally run chmod 777 -R * chown nobody:users -R * in the affected folder. as this is unraids docker safe permissions... did you have all dockers stopped when you ran the tool command? regardless you have a ACL that flagged due to a permission issue.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.