- Smb mac os x mavericks update#
- Smb mac os x mavericks Patch#
- Smb mac os x mavericks upgrade#
- Smb mac os x mavericks windows#
Permission for account 'sis' on share 'smb2test' successfully created! ISILON # isi smb permission create -sharename=smb2test -account-name=sis -account-type=group -permission-type=allow -permission=full ISILON # isi smb permission delete -sharename=smb2test -allĪll permissions for share 'smb2test' successfully deleted! ISILON # isi smb share create -sharename=smb2test -path=/ifs/test/myshare ISILON # mkdir -p /ifs/test/myshare/dirtorename & chown jbdenis:sis /ifs/test/myshare/dirtorename & chmod 2770 /ifs/test/myshare/dirtorename ISILON # mkdir /ifs/test/myshare & chown jbdenis:sis /ifs/test/myshare & chmod 2770 /ifs/test/myshare
ISILON # mkdir /ifs/test & chmod 755 /ifs/test
Smb mac os x mavericks update#
Isilon support will update the SR after the webex session. I'm keeping this information here for everyone. Here are the answer to your last question and the steps we are using to reproduce the problem.
Your question (ie : real example of the problem). I don't have access to OS X mavericks to be sure to answer correctly to We are using LDAP, Isilon ACLs is on "Unix permissions", and we are To AD or are they authenticating with username/password (NTLM) I'll just answer quickly to your questions, maybe it'll help some The help of the support during a webex to be sure you've got all you My colleague will collect all this information for you with > It would be excellent if I had some details on your cluster and client I would be more than happy if this appears to be a Have not seen the same behavior internally on my own 10.9 Macs and OneFS
Smb mac os x mavericks Patch#
To get any valid answers besides "just patch and we'll see from there" =) Indeed, I'm not managing this case on our side, but I'm trying anything I think I found the SR where this issue was reported to Isilon support,Īnd I sent a web note to the contact on that SR, which was not you. The only thing that does not get is setgid on the group, but the ACL will be inherited by new subfiles and subdirectories. Mkdir -p /ifs/test/myshare/dirtorename & \Ĭhown jbdenis:sis /ifs/test/myshare2/dirtorename & \Ĭhmod +a user jbdenis allow generic_all,object_inherit,container_inherit /ifs/test/myshare2/dirtorename & \Ĭhmod +a group sis allow generic_all,object_inherit,container_inherit /ifs/test/myshare2/dirtorename & \ Instead of using Posix mode bits, you'd be setting specific ACLs on the directories. I'm certainly leaning towards Apple bug, but you could adjust the chmod commands slightly to work around this behavior.
Smb mac os x mavericks windows#
The command line, as we've seen, works just fine, as does a Windows client.įorcing the Mac to SMB1 by using cifs:// in the server URL also works, with performance impacts. 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 ACEs for user:jbdenis and group:sis allows for delete_child, but not for std_delete. What you're seeing above is a synthetic ACL that's derived from the Posix mode bits on "dirtorename". It's actually, the lack of std_delete that trips up the Mac. Originally I thought that the problem had something to do with setgid being set on the directory (chmod 2770), but that isn't it. ISILON # ls -led /ifs/test/myshare/dirtorenameĭrwxrws- 2 jbdenis sis 0 Jan 13 16:28 /ifs/test/myshare/dirtorenameĠ: user:jbdenis allow dir_gen_read,dir_gen_write,dir_gen_execute,std_write_dac,delete_childġ: group:sis allow dir_gen_read,dir_gen_write,dir_gen_execute,delete_childĭaniel Pritts, on the Isilon google user groups seems to be able to reproduce the problem on his installation. 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 ?
It seems that SMB2 situation is quite messy on 10.9 right now. I've also posted this question to the Isilon User Group : Google Groupsĭaniel Pritts from the user group reproduced the problem on 7.0.2.4. Side), do you have any feedback on this behaviour ? Problem in their labs (to confirm that this is not a problem on their We are quite stuck here (several weeks since we opened the case).īesides the fact that Isilon support didn't even try to reproduce the The terminal, not in the finder), but Apple does not seem to agree. It looks to me quite obvious that this is an OS X problem (it works in
We've just tried a VMWare Virtual Nodes 7 images, without success.
Smb mac os x mavericks upgrade#
Suggesting an upgrade to 7 because "Isilon did fix lots of things". Installation with various things that didn't help. Working correctly (with very bad performance, seeĪpple told us to ask Isilon, and Isilon support told us to patch our If I force smb1 using smb_neg option in /etc/nf, everything is The share using the finder (the contextual menu does not propose it, If I connect to an smb share, I cannot rename any folder at the root of MacOS X 10.9 (Mavericks) is now using smb2 by default. Isilon OneFS v6.5.5.22 B_6_5_5_244(RELEASE) installed on all nodes.