[6.8.0] File permissions through Samba are set to admin:users and not nobody:users

This is really odd.  I just tested this from my end and it's creating the files on the share with the right permissions.  Can you replicate this behavior with just copying data to a network share the old fashioned way (wondering if your backup software is doing something to the permissions).

 

For me it's also working correctly, I have Synback doing a daily sync from a Windows drive to Unraid and checking latest days after the upgrade permissions are still correct.

I've never had a problem with SMB transfers.  The owner always winds up being my user, not "nobody" but the permissions are always correct so no big deal and something I've never worried about (or cared about)

3 hours ago, jonp said:

This is really odd.  I just tested this from my end and it's creating the files on the share with the right permissions.  Can you replicate this behavior with just copying data to a network share the old fashioned way (wondering if your backup software is doing something to the permissions).

 

When I create a text file using Windows 10 on an SMB share the permissions are set to:
-rw-rw-rw- 1 admin  users    0 Dec 17 16:54 test\ permissions.txt

 

Copying a file from one Unraid server to another:

Source:

-rw-rw-rw- 1 nobody users     18 Dec 17 17:12 test\ permissions.txt

 

Destination:

-rw-rw-rw- 1 admin  users   18 Dec 17 17:12 test\ permissions.txt

 

I am logged into the share using an 'admin' user.

 

 

3 hours ago, jonp said:

(wondering if your backup software is doing something to the permissions).

The software is Acronis backup and I have been using it without seeing this issue for years.  I have a special user that I use to login to the share with Acronis that only has permission to access the backup share.

I've always seen new files created as the user logged into the samba share and group "users", for instance user "wmce", as far back as I can remember. My shares are set as either secure or private.

In case it makes a difference, I have NetBIOS disabled, and WSD enabled.

I'm also seeing some strangeness with CIFS mounts.  Mounting a remote share using CIFS setting the uid=99 and gid=100 should set permissions of nobody:users.

 

/sbin/mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,uid=99,gid=100,,vers=3.0,credentials='/tmp/unassigned.devices/credentials' '//Mediaserver/Public' '/mnt/disks/Mediaserver_Public'

 

When I create a file on the remote share the permissions are set to:

/mnt/disks/Mediaserver_Public - this is the remote share mount point on the local server.
-rwxrwxrwx 1 nobody users      0 Dec 17 16:21 test\ permissions.txt*

 

/mnt/user/Public - this is the remote share on the remote server.
-rw-rw-rw- 1 guest  users      0 Dec 17 16:21 test\ permissions.txt

 

Mounting a remote share using CIFS setting the uid='nobody' and gid='users' should set permissions of nobody:users.

 

/sbin/mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,uid='nobody',gid='users',,vers=3.0,credentials='/tmp/unassigned.devices/credentials' '//Mediaserver/Public' '/mnt/disks/Mediaserver_Public'

 

/mnt/disks/Mediaserver_Public - this is the remote share mount point on the local server.
-rwxrwxrwx 1 nobody users      0 Dec 17 16:32 test\ permissions.txt*

 

/mnt/user/Public - this is the remote share on the remote server.
-rw-rw-rw- 1 admin  users      0 Dec 17 16:32 test\ permissions.txt
 

I would expect all permissions to be nobody:users in all cases.

3 hours ago, Squid said:

I've never had a problem with SMB transfers.  The owner always winds up being my user, not "nobody" but the permissions are always correct so no big deal and something I've never worried about (or cared about)

It's my understanding that Unraid always sets permissions to nobody:users.

44 minutes ago, dlandon said:

It's my understanding that Unraid always sets permissions to nobody:users.

It depends on the user you are using.  If you're not using any login for SMB access, nobody:users is the correct group/user.  However if you authenticate with a user you created called 'admin', files created by that user should show up as that user.  That doesn't mean that other users with access to the share can't access the files.

1 hour ago, jonp said:

It depends on the user you are using.  If you're not using any login for SMB access, nobody:users is the correct group/user.  However if you authenticate with a user you created called 'admin', files created by that user should show up as that user.  That doesn't mean that other users with access to the share can't access the files.

The original post has permissions of 660 and ownership of admin:users.  The login used to access the share for backups is 'home' not 'admin'.  The permissions are 660, not 666 that would allow everyone access.  The computer being backed up is accessing all shares using 'admin', but is using 'home' user for this backup share.

 

You are suggesting this is the Acronis backup?

 

How do you explain this?

I haven't tested 6.7 as it is not possible for me to easily roll back, so I can't confirm it.  Something has changed.

Changed Status to Closed

May I ask why this was closed?  Let us know if there is still something to be investigated here.

I'm closing this until I can better understand what is going on here.  I think the issue is more my ignorance on how permissions and ownership work.

It's also not my expertise, but there's a good post about them on the FAQ:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=546530

 

I should have been clearer.  My issue is more of what Samba is doing to permissions and ownership and/or how Unraid is setting them through Samba.

Yes, that's also explained in that FAQ entry.

I know that I used to run a backup script on my desktop using robocopy.  It would always mess up the permissions on the server, where I couldn't access the files at all without a chmod

7 hours ago, dlandon said:

I'm closing this until I can better understand what is going on here.  I think the issue is more my ignorance on how permissions and ownership work.

Completely understand.  Just didn't want you to think we were brushing this off.  If after more due diligence you think there is a real underlying issue, reopen this report and we'll investigate further.  Thanks again for your help!

stumbled upon this bug report when i noticed the same thing today.  when using private shares, any files written are owned by the logged in user, and not 'nobody', which can cause various annoyances later since so many things assume everything is owned by nobody.

 

i fixed it by modifying the samba config, you can add the following to /boot/config/smb-extra.conf

[global]
  force user = nobody
  force group = users

 

That's my actual solution to the situation as it guarantees the correct permissions on the OS layer. But I understand you can't turn that on users with older data and managed permissions. I'm guessing this can be a Unraid setting, but users should opt-in, unless its a brand new OS config.

 

FYI a lot of NAS use something like that setting to make it easy for the files to be managed, even after migrating the disks out to another OS.