Mac OS Lion SMB vs Fedora 15 SMB, Fail

GrayFox · #1 27th July 2011, 09:10 PM

Grrr,

On my Fedora 15 Box I can mount via smb directories from my Mac Book Pro running
Lion.

The bad news is that I cannot copy files between the two systems via smb.
( I get an operation not implemented error ).

I had to do a 'ssh' type of mount in order to copy the files.

I *can* mount directories from the Fedora box on the Mac and from the
mac I can copy files to and from the two systems.

I know apple has their own smb implementation which is probably the root cause
of the problem.

However I *can* use smb to copy files between the mac and my NAS ( WD My Book Live )

The NAS is running a version of Debian.

I can also copy files between the fedora box and the NAS via SMB.

Is there some kind of configuration glitch?

Thanks for any info...

Jerry

***bob*** · #2 28th July 2011, 12:34 AM

Moved to mac.

nevius · #3 19th August 2011, 02:13 AM

I've been playing around some with Lion. The smb implementation is a little glitchy. You can definitely tell that they rolled their own version for legal rather than technical reasons. I think there was a recent Mac update that was supposed to fix some smb bugs.

smr54 · #4 19th August 2011, 03:18 AM

Lion has some changes in SMB. It breaks--that is, literally breaks, EMC Celerra if Celerra is not patched.

(The other issue we found is that it apparently breaks Cisco's VPN client, however the built in Lion VPN client will work--however, you can't use the encrypted password--though the password is pretty easy to decrypt anyway.)

I've forgotten if it changed behavior by sending a null packet or not sending. Regardless, the change managed to send our EMC into fallover mode.

Now, the other issue is that the kernel upgrades have broken cifs on the Linux end. (Whether it's in cifs utils or the kernel itself, I don't remember. As of kernel 2.6.40, you may have trouble mounting //server/whatever/whenever

However, mount //server/whatever works--it's when you get into multi layered paths that there's a problem. I've only see this on Fedora, as it has a 2.6.40 or higher kernel, and Arch, with the 3.x kernel.

I wonder if it's possible that you're running into that? The way to tell is try to mount a path that is no deeper than //server/share, as opposed to //server/share/subshare.