[SOLVED] nfs mount: No such file or directory ?

czezz · 08-29-2014, 10:18 AM

Im having some odd behavior when try mount NFS share on my Solaris 10.
NFS Server is Linux SUSE and this share I can mount easily on any another Linux box in my network.
However, when I try to mount this same share under my Solaris I get following error.

Code:

# mount -F nfs 10.23.5.30:/var/backups/ /export/home/a
nfs mount: 10.23.5.30:/var/backups/ /export/home/a: No such file or directory

I have no clue whats wrong. I checked paths - all exists.
Any ideas ?

MensaWater · 08-29-2014, 11:09 AM

You verified "/export/home/a" exists on the Solaris server? That appears to be what the message is complaining about.

czezz · 09-01-2014, 08:19 AM

As I have written:

Quote:

I checked paths - all exists.

jlliagre · 09-01-2014, 02:58 PM

It would help if you provide more clues and details about this issue.
Can you for example explain how did you check the paths? i.e. what command(s) you used and what output you got?

czezz · 09-02-2014, 03:41 AM

OK. I think it is all written in my 1st post but let me try again with full details.

This is NFS server: Linux SUSE (SUSE Linux Enterprise Server 11 (x86_64))
IP: 10.23.5.30

Code:

suse1:/var/backups/ # pwd
/var/backups/

suse1:/var/backups/ # ls -al
total 16
drwxrwxrwx 4 nobody nogroup 4096 2014-08-29 17:27 .
drwxrwxrwx 8 sogadm sog     4096 2014-09-02 03:00 ..
drwxr-xr-x 5 root   root    4096 2014-08-25 16:17 CR1
drwxr-xr-x 4 root   root    4096 2014-08-29 17:25 ZH1

This is NFS client: Solaris 10 (Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC)

Code:

[root@solaris1 /export/home/a]# pwd
/export/home/a

[root@solaris1 /export/home/a]# ls -al
total 4
drwxr-xr-x   2 root     root         512 Sep  2 10:28 .
drwxr-xr-x   8 root     root         512 Sep  2 10:28 ..

This is mount command executed under Solaris to mount NFS share from SUSE Linux:

Code:

[root@solaris1 /]# mount -F nfs 10.23.5.30:/var/backups/ /export/home/a
nfs mount: 10.23.5.30:/var/backups/: No such file or directory

jlliagre · 09-02-2014, 05:41 AM

I'm afraid that's not the same error message.

Please copy/paste what is actually written.

pan64 · 09-02-2014, 06:17 AM

you should not stand in the directory (/export/home/a) if you want to use it for mounts.
check if /var/backup really shared

czezz · 09-02-2014, 07:06 AM

Here is screen shot for SUSE Linux (NFS server): https://www.dropbox.com/s/rak5p012oxlbue7/nfs1.PNG?dl=0

Code:

suse1:/var/backups # pwd
/var/backups
suse1/var/backups # ls -al
total 16
drwxr-xr-x  4 root root 4096 2014-09-02 14:13 .
drwxr-xr-x 24 root root 4096 2014-09-02 14:12 ..
drwxr-xr-x  2 root root 4096 2014-09-02 14:13 CR1
drwxr-xr-x  2 root root 4096 2014-09-02 14:13 ZH1

Here is the sitiation on Solaris: https://www.dropbox.com/s/ckep98ce3n...olnfs.PNG?dl=0

Code:

[root@solaris1 /]# pwd
/
[root@solaris1 /]# ls -al /export/home/a/
total 4
drwxr-xr-x   2 root     root         512 Sep  2 10:28 .
drwxr-xr-x   8 root     root         512 Sep  2 10:28 ..
[root@solaris1 /]#
[root@solaris1 /]# mount -F nfs 10.23.5.30:/var/backups/ /export/home/a/
nfs mount: 10.23.5.30:/var/backups/: No such file or directory

I also tried to mount this share on another machine (with RHEL) and it mounts with no problem
@pan64 - im obviously not in the mount point dir. See that prompt is /

MensaWater · 09-02-2014, 07:47 AM

What does "exportfs" with no options output on the NFS server?

What does "showmount <nfs-server>" output on the NFS server? What does the same command output on the target NFS client system?

What does "ping 10.23.50.5" from the NFS client system show?

czezz · 09-02-2014, 07:59 AM

Like I said, I can mount this share form another machine (under RHEL).
Here is an output you ask:
NFS Server

Code:

suse1:~ # exportfs
/var/backups    10.23.5.30/255.255.255.128

suse1:~ # showmount 10.23.5.30
Hosts on 10.23.5.30:
10.23.5.20

NFS Client

Code:

[root@solaris1 /]# showmount 10.23.5.30
10.23.5.20

[root@solaris1 /]# ping 10.23.5.30
10.23.5.30 is alive

MensaWater · 09-02-2014, 08:40 AM

Sorry - command should be "showmount -e" so it shows you what mounts are available that can be seen.

Is the IP of the client in range between 10.23.5.0 and 10.23.5.127? Your export is restricting it to that range?

Is there a firewall running on the client? Does disabling that firewall make it work?

Are you running the NFS client on the client? That is on some OSes like Linux the NFS server and the NFS client are started separately. It has been a while since I did Solaris. Is the RPC daemon running there?

kkuhle · 09-09-2021, 03:39 PM

In case someone comes across this many years later, I found the solution for me on another search result that I cannot link as this is my first post

For me, it was as simple as adding the option `-o vers=3` to the mount command.

This works:

```
bash-3.2# mount -F nfs -o vers=3 server:/shares/data1 /mnt/filer/data1
```

After previously seeing `No such file or directory` response:

```
bash-3.2# mount -F nfs server:/shares/data1 /mnt/filer/data1
nfs mount: server:/shares/data1: No such file or directory
```