Some users unable to access share, AD mode (4.1.9)

I don't believe I mentioned data loss? My concern is having to reapply ownership and permissions on thousands of files, hundreds of folders. That will be a multiple day process.

I backed up the config prior to the 4.1.9 upgrade. I am assuming restoring those won't be helpful either, right? It looks like it is designed to go from one system to another, not fix issues?

If the ownership of existing files has been affected the "Set ownership" option would be a way to fix it. You could try using the Advanced Options tab, but without checking the "Set Ownership..." option. That way you'd change the ownership of the root of the share but not that of existing files within it. Depending on the issue it might not help though.

Perhaps I could SSH in and reset the top level permissions? All of the subfolders, when viewed from the AD server logged in as Administrator (aka root to the ReadyNAS), show the proper permissions on them. It is all a huge mess and like others, I cannot believe this issue was known during beta, made it to final release, and has been continued to be offered for over a month as the recommended upgrade (outside of forum commentary) even though this is a known issue.

We have a second NAS for onsite backups/local redundancy. We did NOT upgrade it to 4.1.9 and I am looking at the settings in Frontview. Those same settings match what is reflected in the primary unit we rolled back to 4.1.8. So I am not sure it is a matter of changing permissions on the Advanced tab.

Per the ReadyNas tutorials on this site, we utilize AD for permissions, set bare minimum permissions on the Share and adjust the folder permissions beneath the share using AD. So primary question would be, does the "known" issue for 4.1.9 pertain to permissions assigned for all files and folders on the NAS itself, or does it also affect AD assigned permissions? As indicated, pulled up in Windows, share permissions from AD server reflect what they were.

Yes you could try doing that via SSH. If you know what you're doing which it sounds like you do that should resolve the problem.

I thought I knew what I was doing until I performed the upgrade without first checking the forums for feedback. That much is on me. I'll try to SSH into the secondary machine and compare share permissions to the primary.

I do see a user indicating they had to reapply permissions over SSH every reboot? Was this simply because they failed to downgrade to 4.1.8 prior to trying this?

Yes on 4.1.9 the problem would reappear every reboot.

Shares.conf match on each server. Linux permissions match for on main shares for each user. Windows Advanced Security Settings for folder matches. What am I missing?

To be clear, I have no had any reported access issues to base shares (e.g."DOCUMENTS" share) or the majority of the folders in it. However, we have a few key folders inside of this share (e.g. "DOCUMENTS\IT") that are inaccessible. These folders ("IT") have identical permissions to our failover/backup NAS (running 4.1.8 without having done 4.1.9 ever).

I know of another share's subfolder (share is "LICENSING", folder is "LICENSING\Faxes") that a user is unable to access since the upgrade yet I and other users are able to hit without error.

Quite perplexing...

What about if you try 4.1.10 beta? 4.1.9+ includes in a major samba update. It's possible that the samba downgrade could be related to the issue.

Would you rate the 4.1.10 beta as being ready for production environment?

Yes