Leopard NFS issue

dexterbip · 11-11-2007, 01:00 PM

As i stated in an earlier post, for some reason the creation of appledouble files on my network volumes is breaking NFS, leaving me unable to write to them.

I thought I'd solved the problem with This Hint, but now they're back and I can't get them to go away. Every time I try to copy a file to my NFS volumes, these files keep getting created. How can I stop this, it's driving me mad?

Edit: Leopard on a Macbook, and NFS mounts created with Directory Utility, in case anyone asks. Could this problem be because I have the NFS volumes hard mounted to specific locations rather then dynamically in /Volumes and so OS X isn't seeing them as network shares?

giskard22 · 11-12-2007, 04:36 PM

I don't think your possible explanation is quite right, but you could be on the right track. Leopard contains a new system for handling automounts, called automount. You may want to investigate its use and see if doing things the new way resolves your problems.

dexterbip · 11-12-2007, 05:45 PM

Hmm, I've investigated a bit further and I suspect you're right and it's possibly something to do with a more entrenched networking problem rather than specifically NFS. I can't see why the AppleDouble files would be causing the problems. I thought it might be a permissions issue to do with the AppleDouble files being created by root and having no_root_squash turned on in my exports. But, in fact, further investigation shows that they're owned by my user account with RW permissions both on the mac and server side.

Interestingly, my mac console logs are frequently showing the following messages:

Code:

Nov 12 01:03:32 James mDNSResponder[16]: getifaddrs ifa_netmask for   fw0(5) Flags 8863 Family  2 169.254.118.28 has different family: 0
Nov 12 01:03:32 James mDNSResponder[16]: SetupAddr invalid sa_family 0

I've a suspicion this might be something to do with it, but I lack to knowledge to be sure. Any ideas anyone?

Edit: could you possibly point me to some info on automount? A google search is proving rather useless as there's so much info on automounting so many different types of shares under leopard that I'm having trouble finding relevant information.

In the mean time I shall read up on automount and look into that to see if I can ferret out any problems there. Ah well, it's all good experience.

giskard22 · 11-12-2007, 05:48 PM

The fw0 interface should be for IP over Firewire. I presume that's got nothing to do with your problem. If you want to stop the messages, I'd disable the interface in Network.

dexterbip · 11-12-2007, 05:49 PM

Oh, yeah, duh. Should have picked up on that one.

RE: my edit above, could you point me towards some info on automount, googling is proving rather fruitless I'm afraid, too much irrelevant information.

dexterbip · 11-12-2007, 06:04 PM

Addendum: Firstly I should state that all my mounts show up just fine in both finder and terminal. I can access the files on them just fine as well. It's only when trying to move or copy files to the server that I have problems. Also, a quick experiment in terminal shows that when I try to copy or move files from the terminal, I get the following error:

Code:

cp: /Users/james/file: could not copy extended attributes to ./file: No locks available

dexterbip · 11-12-2007, 07:03 PM

Further updates:

1. Mods, is it possible to change the title of this thread to simply "Leopard NFS issue" or similar? I'm concerned that the thread title (which I now believe to be at least partially inaccurate) is discouraging people who may be able to help from reading it.

2. Following the above message I'm trying to set my NFS mounts to use the "nolock" option (i've only got one NFS client on my network and I'm never reading files when I'm moving or editing them so this shouldn't be an issue, I believe. however I can't work out how to do this properly. Any guidance would be much appreciated.

dexterbip · 11-16-2007, 01:50 PM

Still having problems with this and can't work out why. What's driving me mad the most is the inconsistency of it. Now I can copy files using the Terminal, which is good, but I don't recall changing anything to make this work, it just does all of a sudden. Also, the problem only seems to apply to certain network volumes.

If I use the finder to copy a file to the locally mounted nfs://server/home/backup then it transfers across fine.

However, try to copy the exact same file to the locally mounted nfs://server/home/Videos and it fails instantly with an "error code -36".

These two mounts have identical mount options in Directory Utility, and identical (barring paths, obviously) lines in /etc/exports on my Linux box.

What on earth can be causing this? Can anyone help at all?

Edit: also the folders on the Linux box side have identical ownership/permissions all the way down the directory trees, in case anyone was wondering.

trevor · 11-16-2007, 03:06 PM

Quote:

Originally Posted by dexterbip


	1. Mods, is it possible to change the title of this thread to simply "Leopard NFS issue" or similar? I'm concerned that the thread title (which I now believe to be at least partially inaccurate) is discouraging people who may be able to help from reading it.

Thread title changed as requested.

Trevor

dexterbip · 11-16-2007, 09:41 PM

Ah, cheers. You're a gent.

giskard22 · 11-16-2007, 10:08 PM

Dexter, my recommendation is to take this query to the macenterprise.org email list. There are some awesome people on there.

11-11-2007, 01:00 PM	#1
dexterbip Triple-A Player Join Date: Nov 2007 Posts: 77	Leopard NFS issue As i stated in an earlier post, for some reason the creation of appledouble files on my network volumes is breaking NFS, leaving me unable to write to them. I thought I'd solved the problem with This Hint, but now they're back and I can't get them to go away. Every time I try to copy a file to my NFS volumes, these files keep getting created. How can I stop this, it's driving me mad? Edit: Leopard on a Macbook, and NFS mounts created with Directory Utility, in case anyone asks. Could this problem be because I have the NFS volumes hard mounted to specific locations rather then dynamically in /Volumes and so OS X isn't seeing them as network shares? Last edited by dexterbip : 11-11-2007 at 01:03 PM.

11-12-2007, 05:45 PM	#3
dexterbip Triple-A Player Join Date: Nov 2007 Posts: 77	Hmm, I've investigated a bit further and I suspect you're right and it's possibly something to do with a more entrenched networking problem rather than specifically NFS. I can't see why the AppleDouble files would be causing the problems. I thought it might be a permissions issue to do with the AppleDouble files being created by root and having no_root_squash turned on in my exports. But, in fact, further investigation shows that they're owned by my user account with RW permissions both on the mac and server side. Interestingly, my mac console logs are frequently showing the following messages: Code: Nov 12 01:03:32 James mDNSResponder[16]: getifaddrs ifa_netmask for fw0(5) Flags 8863 Family 2 169.254.118.28 has different family: 0 Nov 12 01:03:32 James mDNSResponder[16]: SetupAddr invalid sa_family 0 I've a suspicion this might be something to do with it, but I lack to knowledge to be sure. Any ideas anyone? Edit: could you possibly point me to some info on automount? A google search is proving rather useless as there's so much info on automounting so many different types of shares under leopard that I'm having trouble finding relevant information. In the mean time I shall read up on automount and look into that to see if I can ferret out any problems there. Ah well, it's all good experience. Last edited by dexterbip : 11-12-2007 at 05:49 PM.

11-12-2007, 06:04 PM	#6
dexterbip Triple-A Player Join Date: Nov 2007 Posts: 77	Addendum: Firstly I should state that all my mounts show up just fine in both finder and terminal. I can access the files on them just fine as well. It's only when trying to move or copy files to the server that I have problems. Also, a quick experiment in terminal shows that when I try to copy or move files from the terminal, I get the following error: Code: cp: /Users/james/file: could not copy extended attributes to ./file: No locks available

11-16-2007, 01:50 PM	#8
dexterbip Triple-A Player Join Date: Nov 2007 Posts: 77	Still having problems with this and can't work out why. What's driving me mad the most is the inconsistency of it. Now I can copy files using the Terminal, which is good, but I don't recall changing anything to make this work, it just does all of a sudden. Also, the problem only seems to apply to certain network volumes. If I use the finder to copy a file to the locally mounted nfs://server/home/backup then it transfers across fine. However, try to copy the exact same file to the locally mounted nfs://server/home/Videos and it fails instantly with an "error code -36". These two mounts have identical mount options in Directory Utility, and identical (barring paths, obviously) lines in /etc/exports on my Linux box. What on earth can be causing this? Can anyone help at all? Edit: also the folders on the Linux box side have identical ownership/permissions all the way down the directory trees, in case anyone was wondering. Last edited by dexterbip : 11-16-2007 at 01:58 PM.

11-12-2007, 04:36 PM	#2
giskard22 Moderator Join Date: May 2003 Posts: 4,103	I don't think your possible explanation is quite right, but you could be on the right track. Leopard contains a new system for handling automounts, called automount. You may want to investigate its use and see if doing things the new way resolves your problems.

11-12-2007, 05:48 PM	#4
giskard22 Moderator Join Date: May 2003 Posts: 4,103	The fw0 interface should be for IP over Firewire. I presume that's got nothing to do with your problem. If you want to stop the messages, I'd disable the interface in Network.

11-12-2007, 05:49 PM	#5
dexterbip Triple-A Player Join Date: Nov 2007 Posts: 77	Oh, yeah, duh. Should have picked up on that one. RE: my edit above, could you point me towards some info on automount, googling is proving rather fruitless I'm afraid, too much irrelevant information.

11-12-2007, 07:03 PM	#7
dexterbip Triple-A Player Join Date: Nov 2007 Posts: 77	Further updates: 1. Mods, is it possible to change the title of this thread to simply "Leopard NFS issue" or similar? I'm concerned that the thread title (which I now believe to be at least partially inaccurate) is discouraging people who may be able to help from reading it. 2. Following the above message I'm trying to set my NFS mounts to use the "nolock" option (i've only got one NFS client on my network and I'm never reading files when I'm moving or editing them so this shouldn't be an issue, I believe. however I can't work out how to do this properly. Any guidance would be much appreciated.

11-16-2007, 09:41 PM	#10
dexterbip Triple-A Player Join Date: Nov 2007 Posts: 77	Ah, cheers. You're a gent.

11-16-2007, 10:08 PM	#11
giskard22 Moderator Join Date: May 2003 Posts: 4,103	Dexter, my recommendation is to take this query to the macenterprise.org email list. There are some awesome people on there.