New folders and files are read only for other users

[vertices]

ReadyNAS Pro 4 running the buggy 4.2.19.

I have CIFS shares on this box. It seems I simply cannot get new folders to be created that others have access to. Only the creator has read/write and all others have read only.

share name is "s"
Permissions are as follows:
Default Access: Read/Write
Everything blank in Share Access restrictions
Advanced CIFS Permission: Automatically set permissions is checked
Do not allow ACL changes to be more restrictive is unchecked
For both sections under this, all 4 options (both sets of Group Rights and Everyone rights) are set to Read/Write

Under Advanced Options tab
Share folder owner is name of the share (s)
group is nogroup
All 3 boxes are read/write
Grant rename and delete is checked
I've also checked the box to reset ownership and permissions and let it run

When I check the box to reset, it fixes everything that is existing. But as soon as someone makes a new folder or file, it gives only themselves r/w access. All others have only read.

this is driving me crazy as I'm pretty sure this is all set right.

Is this just a bug of 4.2.19? Or am I dong something wrong?

Every file made is 644 and ever folder is 755. If I reset permissions using advanced tab it fixes everything. I can't run this manually every time someone puts up a file or folder.

Thanks.


I also have a problem where everytime I reboot, one of the shares "t" gets mapped to the wrong spot and I have to rename it and then rename it back to get it back to the right spot. Driving me crazy.

[vertices]

I'd like to add that I have 3 shares, S, T, and M.

All 3 are configured the same way.
S has this problem with all new files being 644 and folders 755. I can reset permissions in FrontView and fix all existing files.
T works fine and all new files are 777, but it gets mapped to wrong path at every reboot and I have to rename it every time.
M works fine and all new folders and files are 777. It stays that way even through reboots.

I am really looking for a fix for this.

I am really considering dropping this thing down to 4.2.17 this evening in the hopes that that fixes these issues. Thoughts on that?

[vertices]

Update. I've downgraded to 4.2.17. I have no addons installed. The problem with T remapping at reboot is now fixed.

S and T are now identical in all settings. Permissions have been reset on both.

T works perfectly anywhere. The root of S works perfectly. However if anything gets made in a subfolder on S, it uses 644 permissions for files and 755 for folders. This is driving me crazy.

[vertices]

It appears to be fine with any newly created folders and files. It's only existing ones that cause a problem. So if anyone adds a file to s/licenses then it gets 644 permissions. However if they make a new folder on the root of s, say s/testfolder then make a file in there, it correctly gets 777 permissions. So I can't fix permissions on existing data and resetting permissions does nothing to fix this. I am dealing with 800GB of data so I can't just easily copy and move stuff around.

I can make a new share and copy data into it from a broken share and it works perfectly. Somehow there has got to be a way to fix these broken shares.

Surely someone is an expert on these matters on the boards and has some idea what to do or has seen this before?

[vertices]

Ok well the only thing that seems to work is to copy the files into a new share. Hopefully after doing that and removing the existing share I can simply rename the new one with the old name. But with my luck on this device, I'm guessing that will fail as well.

[irishkeet]

Hello I'm having permission issues with my Pro too, sorry I can offer any help but I would like to say that I cant believe nn one else is offering you an advice, tips or support!

all the best
irishkeet

[jaya]

Hi

I do have the same issue with my Readynas 3200. New folders are only giving read access to other users.

[sycdan]

I had this problem also, but over SFTP (I installed EnableRootSSH; I'm never on the local network, so I don't know if this would apply to CIFS in my case).
The only fix I found was to create a file named ".bashrc" in each user's home directory and add the line "umask 002" to it. It seems that the default umask is set to 022 (in /etc/profile), which results in only the owner having read/write access to new folders.

[vertices]

I should have posted back with my findings but forgot. Essentially what I found after extensive testing, is that you should never, ever, access SMB files shares by authenticating to the ReadyNAS as the admin account. For testing, I made 2 shares that were identical in all respects other than name. I accessed one by the admin account and copied folders into it. I accessed the other by by an account that was a member of the group that was given rights and copied the same folders into it.

On the share that I accessed via the admin account, I ended up with the same problem I outlined in this thread. New folders created in those copied folders didn't have proper permissions. No amount of resetting or chmod would fix it. Ok well technically resetting would fix it, but as soon as another folder went in, it had the same broken permissions as before.

On the share that I accessed only via the account in the right group, the folders always retained proper permissions and new folders were fine. Worked as it was expected to work.

When we set this up originally, we used the admin account to migrate existing data from a Windows file server to this ReadyNAS. This is what caused our issues. So in short, don't ever access a file share with the admin account. It will cause you headaches. Always authenticate to shares with a nonadmin account.

[sycdan]

Good to know. In my case though, I never used the admin account for anything. As I said though, the root of my problem may have been different as I wasn't using CIFS. Glad you figured it out, anyway!