NFS does not work with OS X Mavericks

[Rich Rubasch]

Why am I so attracted to threads that have more than two Bob Zelin posts in them? Because they are a DAMN FINE READ!

Rich Rubasch
Tilt Media Inc.
Video Production, Post, Studio Sound Stage
Founder/President/Editor/Designer/Animator
https://www.tiltmedia.com

[Joakim Ziegler]

I’m running Mavericks on this machine right now, and I have a bunch of NFS shares mounted. I just mount them in a script that’s basically doing

sudo mount -t nfs -o intr,hard,rwsize=32768 resolve02:/data_2 /data_2

And so on for each share.

—
Joakim Ziegler – Postproduction Supervisor

[Georg P. mueller]

Hi Eugeny,
Glad I found this post. Bob mentioned your Avid workflow with the NFS manager. I know this is a FCX forum (and that’s what I usually work with) but I was asked to troubleshoot an Avid shared storage system we setup in Northern Thailand for the production of a Hollywood feature. Right now we are using a mac mini running linux and indiestor – which gives us all kinds of problems when using a mirrored raid drives. The editor is freaking out and we need a fast and solid solution.

Google did not come up with anything usable. Would you mind sharing your Media Composer/NFS Manager experience with me? If this is not the right place to do so you could send me a mail at georg at livingfilms.com

Thanks a lot!

Georg

[Kevin Marinelli]

I had the same issue with NFS. Luckily we have a service contract with Apple, so I was able to get the necessary and undocumented information from them to get NFS to work.

In my case, the NFS mounts were specified in our OpenDirectory server, but the same parameters should work as part of the fsopts in the O/S auto_master file.

Note that Apple only documents “net” as being the only option available in the vfsOpts for NFS automounts. The necessary change was to use the vfsOpts “nosuid nodev multilabel”.

With the vfsOptions changed, everything works like magic. Also note, that you should not mount NFS file systems in /Volumes.

[Steve Modica]

I just had the good fortune to work with a very patient customer in Singapore on this issue.

Bob, make sure your server has rpc.lockd *or* make sure you set “locallocks” in the nfs.conf file. (see the man page for nfs.conf. There’s an options parameter where you can set normal NFS options)

FCP wants to lock the .fcplock file it creates. If you don’t have something enabled so it can, it gets errno 45 (operation not supported) and chokes. The error says the location is already locked by “null”. Very unhelpful.

Steve

Steve Modica
CTO, Small Tree Communications

[David Mendes]

Hi there,

I’m a new user in Creative Cow. Actually in my Company (in Portugal) we work with 3 Computers in FCP 7 (with Lion) and we are thinking to change to FCP X.

Currently we have one of this computers (MAC_01) connected to a RAID 5 (via Mini SAS) with all the projects and folders inside. The other editors – MAC_02 e MAC_03 (and also the MAC_01), can edit directly from the project files via Ethernet Gigabit.

I read many forums and tips to create a new workflow process, but i can’t find a perfect solution until i read the Bob Zelin post “FCP X Add San Location to any shared storage system” (https://forums.creativecow.net/readpost/335/59771).

After read this post i think that my problem was solve, but when i delete any Event from the project, FCPX says “The file couldn’t saved because you don’t have permission. To view or change permissions, select the item in the Finder and Choose File>Get Info. ”

I already try to change the read&write permissions manually in finder to all users but didn’t solve the problem. I’m using the app “NFS Manager” with this settings:

NFS Server – SHARE DEFINITIONS

Shared Folder
/Volume/RAID5/FCPX_Server

OPTIONS
Share “read only” – disabled
Allow Clients to also mount objects in the shared folder – Enabled

User Mapping: I already try Map “root”, Map All Users and Don’t Map Users

Minimum Security: System standard only

Access Permission: Allow access from any network and computer

I didn’t change any other menu. Can anyone help me to understand what is missing?

I already read this solution is not working well in Mavericks. I’am thinking to install it too when change all the workflow, but i think isn’t a good idea if this solution only works with Lion/Mountain Lion…

With you (in Lion or Mountain Lion) that solution works at 100% in no fails or limitations??

I hope you can help me because my eyes are already red for reading so many posts, blogs ans forums… I can’t understand how Apple can make such a thing…

Best Regards,
David Mendes

[Steve Modica]

I have a feeling the server isn’t running rpc.lockd. Without that, FCP can’t create it’s .fcplock file. You need to edit /etc/nfs.conf and put in the option for locallocks. See the man page for nfs.conf. There’s a parameter in there for setting standard nfs options. You need “locallocks”

Steve Modica
CTO, Small Tree Communications

[Chris Murphy]

If the server is NFSv4, rpcbind, lockd, and statd aren’t running. I haven’t tested it, but I figured by Mavericks NFSv4 would be the default, as it’s been around for 11 years already. If not, the command would be a variant of ‘sudo mount_nfs -o vers=4’ and since it uses TCP, rwsize defaults to 32KB. It might still be worth increasing the readahead value from the default of 16, and async if the proper precautions are taken and the risk is understood.

[Steve Modica]

I tried nfsv4 and it hangs pretty quickly (probably trying to do locking). I haven’t investigated yet.

Steve Modica
CTO, Small Tree Communications

[Chris Murphy]

OK so I’ve played with this on 10.8.5 and I’m getting some fairly craptastic behavior.

Without sudo I can cp read or write a file from/to an NFS share without difficult, and with OK performance. However I can only read/copyfrom the Finder. I can’t write files from the Finder or from other apps.

When I try to Finder copy a file to an NFS share, I get a beachball. If I try to cancel, the copy dialog says “Stopping…” for 10+ minutes and doesn’t recover. Console reports:

kernel: nfs4_setclientid: client ID in use?
kernel: nfs4_setclientid failed, 10017
kernel: nfs mirror mount of 192.168.1.137:/chris on /Network/f20/chris failed (10017)

And it repeats. I think this is a UID/GUID mapping problem, although I don’t know why the Finder is being such a misbehaving ill tempered dick about it when cp has no problem. Irritating.