NFS client write permissions

tireseas · 05-02-2005, 07:21 AM

Hi

I am mounting a directory from a Slack 10.0 to a Slack 10.1 box. The drive mounts just fine except for a permissions error kicked up on the client machine (10.1 box) when I want to write to the drive.

The /var/lib/nfs/etab file on the server reads:

Code:

/home/myself/SHAREZ
192.168.1.20(rw,sync,wdelay,hide,nocrossmnt,secure,no_root_squash,no_
all_squash,subtree_check,secure_locks,mapping=identity,anonuid=-2,anon
gid=-2)

What else should I be checking to provide the client permission to modify shared files or create new files/directories on the NFS drive?

TIA

acid_kewpie · 05-02-2005, 08:18 AM

why are you using all those options?? looks like you just clicked every box or added every option you could see.... just use rw,sync options.

tireseas · 05-02-2005, 09:28 AM

Quote:

acid_kewpie wrote:
why are you using all those options??

Actually, those tend to be the default settings on NFS as far as I can tell. In any event, even specifying simply rw,sync in the /etc/exports and mounting the drive again yields the same problem, i.e.

Code:

touch: cannot touch '/mnt/SHAREZ/test.txt': Permission denied

Back to square one. Any one else have any ideas?

Thanks

acid_kewpie · 05-02-2005, 03:20 PM

Those aren't default options at all... there really aren't any default options, as it's so basic. something like "no_root_squash" opens up HUGE security issues, that's no default.

well then that should be all you need for the NFS stage. The great thing about NFS is that it's still unix level all the way, obviously unlike samba, SO... if you have a permission denied chances are it's due to existing serverside filesystem permissions, and not related to NFS at all.

tireseas · 05-02-2005, 04:53 PM

Quote:

Originally posted by acid_kewpie
Those aren't default options at all... there really aren't any default options, as it's so basic. something like "no_root_squash" opens up HUGE security issues, that's no default.

hmmmm .... according to both the man pages as well as http://www.troubleshooters.com/linux/nfs.htm it would appear that there are some defaults, viz.

secure;
ro;
sync (for versions post 1.0.0);
nohide

In addition to these certain defaults can be explcitly stated.

This was taken from the man pages, which would seem to suggest that there are defaults ... so what do you mean when you write that there are no defaults? What are you referring to?

Quote:

SO... if you have a permission denied chances are it's due to existing serverside filesystem permissions, and not related to NFS at all.

OK ... so you mean that the server side directory being exported needs to have its permissions modified in order to allow the client to write to that directory as well? Would that be world-writable or group writable or user writable? Would there be any settings/permissions to modify on the client side?

TIA

acid_kewpie · 05-03-2005, 07:52 AM

the access rights model over NFS is exactly the same as a native Unix filesystem. NFS has no right to override local file system attributes. it's not a case of making it world writable etc... just complaing with whatever conventional Unix permissions.