#1 2021-08-19 20:44:52

jjanderson5

Member

Registered: 2016-05-10

Posts: 155

[SOLVED] requested NFS version or transport protocol is not supported

I recently entered a similar problem (https://forums.bunsenlabs.org/viewtopic.php?id=7742) where I was not able to mount a host using nfs. There was a problem in my /etc/exports file and when that was corrected, the mount command worked as expected.

Using the same PC, I am now trying to mount a file system from 3rd host, 'roe'. I have already reviewed the /etc/exports file and it looks ok, but I am getting the same error message as before:

requested NFS version or transport protocol is not supported

I am working on a host name 'cimoli' and trying to mount the host 'roe' with the command:

cimoli: sudo mount -t nfs roe:/home /mnt/roe

The /etc/exports file on roe reads at follows:

/home       192.168.1.254(rw,no_subtree_check)
  ...
/home       192.168.1.237(rw,no_subtree_check)
  ...

where 192.168.1.237 is the IP address of 'cimoli'. When I run:

ls -ld /mnt/roe

the output is:

drwxr-xr-x 2 root root 4096 May  2 07:33 /mnt/roe

I obviously have a mistake in my setup, but it is not jumping out at me. Any suggestions on what I should check next?

Last edited by jjanderson5 (2021-08-20 21:41:21)

rbh

Moderator

From: South of Lapplands inland

Registered: 2016-08-11

Posts: 1,921

Re: [SOLVED] requested NFS version or transport protocol is not supported

Yes, twice you have asked for help with simple syntax error in /etc/exports.

Now it works ok on the server and at least one client, but you can not adapt the client configuration on another client?

You can from server and client (both working and faulty) list server export?

showmount -e # on server "roe"
showmount -e roe # on client

You can check status of nfs services.
Command "systemctl | grep nfs", lists all nfs services.
What is status for NFS Mount Daemon; nfs-mountd.service

systemctl status nfs-mountd.service

In your mount command "sudo mount -t nfs roe:/home /mnt/roe", you have the name of the server:roe. Can you ping roe? if not, add roe to file /etc/hosts or in mount command, use the ip-adress.

You are still using a very long export list. I previosly wrote, that you can export to the whole lan: 192.168.1.0/24 in one row.

Last edited by rbh (2021-08-19 22:46:48)

---

// Regards rbh

Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu

ohnonot

...again

Registered: 2015-09-29

Posts: 5,592

Re: [SOLVED] requested NFS version or transport protocol is not supported

requested NFS version or transport protocol is not supported

The message is clear. Assuiming your /etc/exports does not contain any syntax errors this time, and seeing that you haven't specified the NFS version, you need to figure out which version both client & server default to.
Also consider /etc/fstab on both sides (at least that's how my NFS stuff is set up).

jjanderson5

Member

Registered: 2016-05-10

Posts: 155

Re: [SOLVED] requested NFS version or transport protocol is not supported

@ohnonot

using nfsstat the version on both client and server is v4.

In /etc/fstab, there is no reference to the host being mounted, i.e. roe, so I'm ruling out /etc/fstab as a possible problem. That was worth checking. Thanks for the hint.

jjanderson5

Member

Registered: 2016-05-10

Posts: 155

Re: [SOLVED] requested NFS version or transport protocol is not supported

@rbh

As you suggested, I ran:

systemctl status nfs-mountd.service

and got:

  proc-fs-nfsd.mount loaded active mounted  NFSD configuration filesystem
  nfs-blkmap.service loaded active running  pNFS block layout mapping daemon
● nfs-server.service loaded failed failed   NFS server and services
  nfs-client.target loaded active active    NFS client services

I started the nfs server and that fixed my problem.

In past releases, when the nfs server was running, a more accurate error message was given. I consider the error message given, i.e. nfs version or transport protocol not supported, to be a bug and plan to enter a report in bugzilla when I have some free time.

Regarding the long export list, my apologies. I vaguely remember you mentioning 192.168.1.0/24, but I did not make a note at the time. I have put a note on my desk, and I will start including this IP addr in my exports file.

As usual, thanks to you and ohnonot!!