jbdenis wrote:  ISILON # ls -led /ifs/test/myshare/dirtorename                                                                                             drwxrws---    2 jbdenis  sis  0 Jan 13 16:28 /ifs/test/myshare/dirtorename  OWNER: user:jbdenis GROUP: group:sis SYNTHETIC ACL 0: user:jbdenis allow dir_gen_read,dir_gen_write,dir_gen_execute,std_write_dac,delete_child  1: group:sis allow dir_gen_read,dir_gen_write,dir_gen_execute,delete_child    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:  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.
Hi everybody,  We are using OneFS 6.5.5.22 :  Isilon OneFS v6.5.5.22 B_6_5_5_244(RELEASE) installed on all nodes. Disk_Firmware_1.6 - installed patch-111687 - installed patch-113108 - installed IsiFw_Package_v8.3 - installed patch-113513 - installed  MacOS X 10.9 (Mavericks) is now using smb2 by default.  If I connect to an smb share, I cannot rename any folder at the root of the share using the finder (the contextual menu does not propose it, same thing when I click on the name). I can do it using mv in /Volumes/myshare with a terminal.  If I force smb1 using smb_neg option in /etc/nsmb.conf, everything is working correctly (with very bad performance, see [URL]#!topic/isilon-user-group/YU5yXmpTax0).  Apple told us to ask Isilon, and Isilon support told us to patch our installation with various things that didn't help. Now, they're suggesting an upgrade to 7 because "Isilon did fix lots of things". We've just tried a VMWare Virtual Nodes 7 images, without success.  It looks to me quite obvious that this is an OS X problem (it works in the terminal, not in the finder), but Apple does not seem to agree. We are quite stuck here (several weeks since we opened the case).  Besides the fact that Isilon support didn't even try to reproduce the problem in their labs (to confirm that this is not a problem on their side), do you have any feedback on this behaviour ?  I've also posted this question to the Isilon User Group : Google Groups  Daniel Pritts from the user group reproduced the problem on 7.0.2.4.   It seems that SMB2 situation is quite messy on 10.9 right now. I just need a CLEAR status from EMC/Isilon on this problem : where is the problem, is it working on, is there an ETA for the resolution ?  Jean-Baptiste
Mavericks OS X 10.9 / SMB2 / Finder : cannot rename