Daniel Pritts, on the Isilon google user groups seems to be able to reproduce the problem on his installation.
Originally I thought that the problem had something to do with setgid being set on the directory (chmod 2770), but that isn't it. It's actually, the lack of std_delete that trips up the Mac. What you're seeing above is a synthetic ACL that's derived from the Posix mode bits on "dirtorename". The ACEs for user:jbdenis and group:sis allows for delete_child, but not for std_delete. The Mac seems to need std_delete to be in the ACL in order for the Finder to give the user the option to rename. The command line, as we've seen, works just fine, as does a Windows client.
Forcing the Mac to SMB1 by using cifs:// in the server URL also works, with performance impacts.
I'm certainly leaning towards Apple bug, but you could adjust the chmod commands slightly to work around this behavior. Instead of using Posix mode bits, you'd be setting specific ACLs on the directories. Something like this could be done:
I think I found the SR where this issue was reported to Isilon support, and I sent a web note to the contact on that SR, which was not you. I have not seen the same behavior internally on my own 10.9 Macs and OneFS 6.5 or 7.0.
At first guess, this looks as if Finder is misinterpreting permissions, but what I see from the customer in that other SR looks normal to me, and shouldn't cause problems for the Finder.
It would be excellent if I had some details on your cluster and client configuration so I can reproduce this. Are your Macs and cluster joined to AD or are they authenticating with username/password (NTLM) credentials? What are the permissions on your share, and what are the permissions on the folders in the share? You can get those details with this:
isi smb permission list --sharename=
ls -led
I'd also like to see ls -led of the parent folder in that SMB share.
I also commented on this in the Google group. This is an OSX 10.9 issue - still present in 10.9.1. There have been numerous reports of this behavior, against many NAS platforms (including actual Windows Server) with SMB2. The known/solid workaround is to revert to SMB1 workflow.
I don't quite understand why the community views this as an 'Isilon problem'. Certainly, workflows are disrupted and Isilon behavior is affected, but in terms of product defect, clearly this is an Apple defect, based on all the public evidence.
here are the answer to your last question and the steps we are using to reproduce the problem. I'm keeping this information here for everyone. Isilon support will update the SR after the webex session.
Permission for account 'sis' on share 'smb2test' successfully created!
ISILON # isi smb permission list
--sharename=smb2test
SMB Share Permissions:
Sharename: smb2test
Account Acct Type Perm Type Permission
sis Group Allow Full
If I connect to this share using OS X 10.9 Mavericks, I cannot rename the "dirtorename" folder (information panel is grayed out, nothing happen if I click on the name of the directory). I cannot rename the directory using a Windows 7 client.
Daniel Pritts, on the Isilon google user groups seems to be able to reproduce the problem on his installation.
> Certainly, workflows are disrupted and Isilon behavior is affected, but in terms of product defect, clearly this is an Apple
> defect, based on all the public evidence.
I would be more than happy to have an official statement from Isilon support and deal with other things. But we were suggested to apply patch (which we did), and even a OneFS 6 -> 7 update. Also, why Bernard Case couldn't reproduce this problem ?
Could you give me some pointers that show people having the exact same problem ? Indeed, the public evidence you can found on smb2 and Mavericks is quite important, but I didn't really find anything like the problem I've got.
Your case one that illustrates a larger Apple problem; the relationship of the Finder, SMB2 and permissions handling therein. Renaming is merely updating file metadata, and the Finder has problems dealing with the root of an SMB2 share and the saving of files. In your case, you are saving metadata. You are also using LDAP which many of the others don't, but that is about authentication, not necessarily SMB2/Finder permissions handling, which is the core of the Apple problem (pun intended)
The advice the Isilon support people gave you is sound.
You yourself admitted this in your original post:
"It looks to me quite obvious that this is an OS X problem (it works in the terminal, not in the finder),"
Bingo.
Your best resource at this point, in my opinion, is to use the known workarounds or place your business emphasis (read: customer pressure) towards Apple support. It is there in which you will solve the problem. If it's any consolation, you have quite a bit of company.
Thank you for the pointer. Not easy to spot what you're talking about, is that in the comments ?
"It looks to me quite obvious that this is an OS X problem (it works in the terminal, not in the finder),"
Indeed. Since we already opened a case at Apple and the answer was just "Contact EMC", I'm looking for an official statement or more basically, confirmation of EMC and help to make Apple accept our problem. I guess EMC has more power than me regarding Apple. I'm just insisting because I just want to have an official clear answer to show for Apple, that's all. And having a customer patch its Isilon cluster to deal with this specific problem although you seem to know that it won't do anything about it is quite... disappointing.
> If it's any consolation, you have quite a bit of company.
Do you have any opened case with Apple at the moment regarding this problem ?
> The Mac seems to need std_delete to be in the ACL in order for the Finder to give the user the option to rename.
Thank your for this analysis.
> I'm certainly leaning towards Apple bug,
Ok. Did Apple confirm this to EMC ? I mean, the lack of std_delete that trips up the Mac is really something the Finder should not interpret the way it does now or should the Isilon cluster show this option to the mavericks client ? The fact that Finder add its own business logic (it works from the mavericks CLI) is quite disturbing, but it seems to be the case.
> but you could adjust the chmod commands slightly to work around this behavior.
> Instead of using Posix mode bits, you'd be setting specific ACLs on the directories.
> The only thing that does not get is setgid on the group, but the ACL will be inherited by new subfiles and subdirectories.
The combined fact that we are not in our comfort zone regarding ACLs (besides POSIX) and that we allow symetric access between CIFS and NFS protocol (users could to their own chmod/chown etc...) mean that we cannot implement this solution without documenting ourselves and evaluate with care the impact on our users
BernieC
76 Posts
2160
0
Posted January 13th, 2014 10:00
Originally I thought that the problem had something to do with setgid being set on the directory (chmod 2770), but that isn't it. It's actually, the lack of std_delete that trips up the Mac. What you're seeing above is a synthetic ACL that's derived from the Posix mode bits on "dirtorename". The ACEs for user:jbdenis and group:sis allows for delete_child, but not for std_delete. The Mac seems to need std_delete to be in the ACL in order for the Finder to give the user the option to rename. The command line, as we've seen, works just fine, as does a Windows client.
Forcing the Mac to SMB1 by using cifs:// in the server URL also works, with performance impacts.
I'm certainly leaning towards Apple bug, but you could adjust the chmod commands slightly to work around this behavior. Instead of using Posix mode bits, you'd be setting specific ACLs on the directories. Something like this could be done:
mkdir -p /ifs/test/myshare/dirtorename && \
chown jbdenis:sis /ifs/test/myshare2/dirtorename && \
chmod +a user jbdenis allow generic_all,object_inherit,container_inherit /ifs/test/myshare2/dirtorename && \
chmod +a group sis allow generic_all,object_inherit,container_inherit /ifs/test/myshare2/dirtorename && \
chmod -a# 2 dirtorename
The only thing that does not get is setgid on the group, but the ACL will be inherited by new subfiles and subdirectories.