We have Fluid FS 4.0.210020 (storage centre on 6.5.20.18 on Compellent SC4020).
Our Windows Home Folders are on an SMB share on our FS8600.
They have rights assigned at home folders root of Creator/Owner Full Control to subs and files only as per Microsoft recommendation.
New users, who via Group Policy redirection, create their Home Folder at first logon, create the redirected sub folders and then, for any files and folders written, they are the owner and have the Owner ACE visible at folder and file level as expected with Full Control permission.
However, if we robocopy or richcopy users home folders into that folder structure, even though Creator/Owner is inherited and you can see permissions and the owner as expected at FOLDER level, at file level you do not see the automatically created ACE in the name of the owner, you see Creator/Owner Full Control instead. The owner however has no effective rights at all.
The same applies when you rename an EXISTING users folder where they get married etc and the owner is changed and set to apply to all child objects. The owner is seen to be changed on all files and folders, BUT, file level permission for the owner is not there.
It seems that there is a bug where this happens with NFS and Fluid FS v5 fixes it. And that this should also resolve the same issue with SMB shares. But, I'd like to know if anyone has encountered this Creator/Owner issue and seen the upgrade fix it please.
The Fluid FS team are unfortunately unable to test this for me with v4 and then v5 at the moment, so I was hoping someone else has encountered and resolved this same issue.
We have 7000 users, and run a 24/7 NHS organisation, we have 9TB of Team Data published via our FS8600 where Creator/Owner isn't used and therefore isn't an issue. We have 2000 home folders currently using the FS8600 too (using DFS) (as yet to migrate 5000 others). If I apply the upgrade, I need to arrange service downtime to accommodate the several seconds to minutes of lost NAS connectivity, which is doable, but it would be good to know if its likely to fix the issue.
Any feedback welcomed. Thanks...