Setting up NSFV4.2 with Yast2 connected but no write permission.

English Network/Internet
1

I have NFS Server set up on remote machine using Yast2 with the domain name “localdomain” all as in the documentation. When I then went to client machine hoping to see the served directory I had the No server found message.

I found the following thread here:-

https://forums.opensuse.org/showthread.php/555943-How-to-set-up-NFSv4-Server-through-YaST2?highlight=NFSv4

but before trying to set up a share manually I tried forcing use of NFSv4.2 and then used then went back to Select button to create a client connection. On this occasion my exported share was available. Hoorah!

My firewall has nfs allowed and port 2049 opened.

My problem is that I have no write permission when looking at the shared directories from Dolphin. The mount is shown with rw permissions.

Where am I going wrong please?

2

Please show the /etc/fstab entry!

cat /etc/fstab | grep nfs

and how it is mounted

mount | grep nfs

And owner/permissions of the mount point

ls -ld /..........

And from the NFS server, how it is exported:

cat /etc/exports

And owner/permissions of the exported directory

ls -ld /......
3

Hi Henk,
These are the results from the client machine.
I have to go to place to get the server info so will reply from there.

alastair@HP-Z640-1:~> cat /etc/fstab | grep nfs    
192.168.169.134:/multimedia                /home/alastair/mastermedia  **nfs**    **nfs**vers=4.2                   0  0 
alastair@HP-Z640-1:~> 



alastair@HP-Z640-1:~> mount | grep nfs 
192.168.169.134:/multimedia on /home/alastair/mastermedia type **nfs**4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clienta
ddr=192.168.169.137,local_lock=none,addr=192.168.169.134) 
alastair@HP-Z640-1:~> 



alastair@HP-Z640-1:~> ls -ld /home/alastair/mastermedia 
drwxrwxr-x 4 alastair users 52 Feb 22  2016 **/home/alastair/mastermedia** 
alastair@HP-Z640-1:~>

I believe this is what is wanted and looks OK to me.

4

Hi Henk,
On the client machine this tells me what I was looking for. Here are the exports:-

alastair@ibmserv2:~> cat /etc/exports 
/home/alastair/Mastermedia      *(ro,root_squash,sync,no_subtree_check) 
alastair@ibmserv2:~>

I couldn’t work out why I had ro for the export so, in Yast, I went to the share. The problem was that the window box that was opened by Yast for options was shorter than the line of default options and had been truncated by the relevant characters. When I scrolled back all was revealed. I am not surprised by the default being ro but didn’t anticipate that the first part of the line was hidden.

Having edited the options on the server and rebooted the client all is now well and thanks again for the help. I wouldn’t have found it myself but am not sure I understand why a reboot was needed on the client. I log out and in was not sufficient.

Many many thanks again.
Budge.

5

Yes, that looks fine to me also. It is not mounted ro and alistair:users is owner and has permissions in that directory.

Thus, alistair must be able to write in that directory. Try that with e.g.

touch /home/alastair/mastermedia/tttest

or, when alistair is in his home directory:

touch mastermedia/tttest

Should be possible.

(PS, do not forget to remove after the test

rm mastermedia/tttest

)

6

Sorry, my post above was posted before your last post.

Do I understand that you had first ro in the exports ebtry? And that by changing that to rw all is fine now.
Then congratulations.

I do not quite understand why you talk about Windows now???

BTW, these things are called “exports”, not “shares” >:)

7

/home/alastair/Mastermedia *(ro,root_squash,sync,no_subtree_check)

Exported as read only, not read write rw?

8

Hi Henk and Sauerland, I have the export working now. The window I refer to is the Options window in the Yast tool for creating NFS export. I didn’t see the full default options line.
Now back to work!
Regards,
Budge.