For whatever reason, a few file system sub-folders were no longer accessible via anyone or any account. We also could not reset permissions or take ownership. We suspected an admin inadvertently messed up the permissions of the folders, but not positive.
With the assistance of a Linux admin and the root account, we navigated the control station CLI to /nas/quota/slot_2/root_vdm_#/ and to the specific folder(s). Editing permissions here also did not work for regaining access via Windows.
In the CS CLI, we could access the problem folders, so we just created a new parent folder, moved the content to it, deleted the original folder, then renamed the new folder to the original name.
I am not sure if this was the best solution, but it did the trick.
Attempting to take ownership was previously attempted and failed. We had a couple of Windows Administrators attempt every way they could think of to access these folders, with no luck. We are wondering if there was some other problem (corruption?) and not just Domain Admin permissions removed.
We actually found a solution that I will post shortly.
As Rainer said, taking ownership by an administrator is the correct procedure as "quota" on the CS is not for data manipulation (though it helped here).
I think if you "unjoin" and re "join" the CIFS server (Unisphere) to the Active Directory, it may add the domain admin again to the CIFS Servers local admin group (and allow the domain admins to take ownership/fix the ACLs).
bryan_washburn
42 Posts
3361
0
Posted August 23rd, 2017 21:00
Follow up…
For whatever reason, a few file system sub-folders were no longer accessible via anyone or any account. We also could not reset permissions or take ownership. We suspected an admin inadvertently messed up the permissions of the folders, but not positive.
With the assistance of a Linux admin and the root account, we navigated the control station CLI to /nas/quota/slot_2/root_vdm_#/ and to the specific folder(s). Editing permissions here also did not work for regaining access via Windows.
In the CS CLI, we could access the problem folders, so we just created a new parent folder, moved the content to it, deleted the original folder, then renamed the new folder to the original name.
I am not sure if this was the best solution, but it did the trick.