[SOLVED] NFS share is mounted as read-only even if write permissions are set

[vofka]

Hello to everybody, under Fedora 12 i try to configure NFS server. On the server machine i configured the share folder as:
/test 192.168.1.100(rw,sync)
restart server /sbin/service nfs restart
make exportfs
on client machine
mount share as:
mkdir /mnt/nfs
mount 192.168.1.100:/test /mnt/nfs
it mounted successful.
However if open the folder /mnt/nfs, i have only read-only permissions.
- The same as if set the remote user as local system user:
/test 192.168.1.100(rw,sync,no_root_squash)
- The same if set the user to folder on server as nfsnobody, after mount it on client i get the same problem. The permissions of folder /test are Write and delete (777) and for all enclosed files

[robertp1984]

I would suggest mounting like this:

mount -o rw 192.168.1.100:/test /mnt/nfs

If this does not help then can you run post the output of:

cat /proc/mounts
ls -la /test   <---- on server
ls -la /mnt/nfs <---- on client

And can you create/modify the files on the server in directory /test?

[sej7278]

what are the permissions on the mountpoints?: ls -ld /mnt/nfs

[stevea]

Originally Posted by vofka

Hello to everybody, under Fedora 12 i try to configure NFS server. On the server machine i configured the share folder as:
/test 192.168.1.100(rw,sync)
restart server /sbin/service nfs restart
make exportfs
on client machine
mount share as:
mkdir /mnt/nfs
mount 192.168.1.100:/test /mnt/nfs
it mounted successful.
However if open the folder /mnt/nfs, i have only read-only permissions.
- The same as if set the remote user as local system user:
/test 192.168.1.100(rw,sync,no_root_squash)
- The same if set the user to folder on server as nfsnobody, after mount it on client i get the same problem. The permissions of folder /test are Write and delete (777) and for all enclosed files

The highlighted parts above require an explanation on your part.
What does "configure the share folder" mean to you - be specific.
"make exportfs" isn't a valid command nor meaningful. What are you trying to say ?
What do you mean "have only read-only permissions" ? read-only is a mount condition, not a permission.

IOW you have given a mish-mash of confusing non-informaiton, and no one can guess what you really mean.


Post the output of the following:
On server, as root:
exportfs -v
ls -ld /test # or whatever the share directory is called


On the client, as root:
ls -ld /mnt/nfs
mount | grep nfs

Then try to create a file on the client showing the complete output of these two commands:
id
touch /mnt/nfs/foo

[vofka]

Originally Posted by sej7278

what are the permissions on the mountpoints?: ls -ld /mnt/nfs

Permissions of mountpoint are:

[root@localhost /]# ls -ld /mnt/nfs
drwxrwxrwx. 2 root root 4096 2010-04-14 02:10 /mnt/nfs

---------- Post added at 12:33 AM CDT ---------- Previous post was at 12:11 AM CDT ----------

Originally Posted by robertp1984

I would suggest mounting like this:

mount -o rw 192.168.1.100:/test /mnt/nfs

If this does not help then can you run post the output of:

cat /proc/mounts
ls -la /test   <---- on server
ls -la /mnt/nfs <---- on client

And can you create/modify the files on the server in directory /test?

unfortunately the mount command with rw option not helped it is still read only.

cat /proc/mounts show the following:
.........................................
192.168.1.16:/test /mnt/nfs nfs rw,relatime,vers=3,rsize=65536,wsize=65536,namlen= 255,hard,proto=tcp,port=65535,timeo=600,retrans=2, sec=sys,mountaddr=192.168.1.16,mountvers=3,mountpo rt=52936,mountproto=udp,addr=192.168.1.16 0 0

---------------------------------------------
ls -la /test <---- on server

[root@localhost ~]# ls -la /test
total 8
drwxrwxrwx. 2 root root 4096 2010-04-11 20:04 .
dr-xr-xr-x. 23 root root 4096 2010-04-13 01:14 ..
-rw-rw-rw-. 1 root root 0 2010-04-11 20:04 test

ls -la /mnt/nfs <---- on client

[root@localhost /]# ls -la /mnt/nfs
total 8
drwxrwxrwx. 2 root root 4096 2010-04-11 20:04 .
drwxrwxrwx. 3 root root 4096 2010-04-11 18:03 ..
-rw-rw-rw-. 1 root root 0 2010-04-11 20:04 test

(Command executed after mounting)

As you can see the permissions are the same. Moreover rw permissions for other users, however, if i try to modify the file test that is inside the mounted /test directory it write me that it is read-only. How can it be so?

---------- Post added at 12:56 AM CDT ---------- Previous post was at 12:33 AM CDT ----------

Originally Posted by stevea

The highlighted parts above require an explanation on your part.
What does "configure the share folder" mean to you - be specific.
"make exportfs" isn't a valid command nor meaningful. What are you trying to say ?
What do you mean "have only read-only permissions" ? read-only is a mount condition, not a permission.

IOW you have given a mish-mash of confusing non-informaiton, and no one can guess what you really mean.


Post the output of the following:
On server, as root:
exportfs -v
ls -ld /test # or whatever the share directory is called


On the client, as root:
ls -ld /mnt/nfs
mount | grep nfs

Then try to create a file on the client showing the complete output of these two commands:
id
touch /mnt/nfs/foo

Yes, the descriptions of problem a bit not precision, it is my fault

on server the output shows following:

root@localhost ~]# exportfs -v
/test 192.168.1.15(rw,wdelay,root_squash,no_subtree_chec k)

[root@localhost ~]# ls -ls /test
total 0
0 -rw-rw-rw-. 1 root root 0 2010-04-11 20:04 test

On client:
[root@localhost /]# ls -ld /mnt/nfs
drwxrwxrwx. 2 root root 4096 2010-04-11 20:04 /mnt/nfs

[root@localhost /]# touch /mnt/nfs/foo
touch: cannot touch `/mnt/nfs/foo': Read-only file system

As you can see the root_squash means that client is mapped user to nfsnobody which have permissions for other , which are rwx. So it is very interesting, why touch write: touch: cannot touch `/mnt/nfs/foo': Read-only file system. Explain me please?

Ans additionally the interesting part of that problem: if on server machine for folder /test i set Owner: nfsnobody permissions: rwx. Set group: nfsnobody with the samer permissions, than mount the folder onclient, i get still read-only problem ))

[jpollard]

Minor typographic error you missed the "d" in the "ls -ls /test" - that
should be "ls -ld /test"

[vofka]

Guys! Thanks everybody! The problem was in Host name address.
The client ip was:192.168.1.15.
Server ip address:192.168.1.16.
The problem was in the following line:
/test 192.168.1.16(rw,wdelay,no_root_squash,no_subtree_check)
I thought that Host must be the host name of server, on which the /test folder is exists.
However it must be - the hosts permitted to access folder! So the ip must be ip of client (192.168.1.15).
So lets assume the problem as closed.