Permission denied when mounting dir

[Brecht De Baets]

We have a HP-UX B.11.23.
We had a couple of mounts on this system, which were working well.
Suddenly we had a problem with one of the mounts : 'Stale NFS file handle'.
I have unmounted this dir, but when I try to mount this directory again, I get the following error : 'Permission denied'.

There are two remarks I would like to make :

1)Our fstab-file looks as this :

192.191.191.202:/efsd11 /mnt/efsd11 nfs rw,suid 0 0
192.191.191.202:/efsd12 /mnt/efsd12 nfs rw,suid 0 0
192.191.191.202:/efsd13 /mnt/efsd13 nfs rw,suid 0 0

The thing is, that the dirs efsd11 and efsd12 are working ok, but the dir efsd13 gives the problem.

2)We also have a separate linux system, where
these 3 dirs are mounted correctly (efsd13 also). So on that machine we don't have a problem !

What could be the problem ?

[Matti_Kurkela · Accepted solution]

Things to check:

- DNS or any other means of hostname resolution: if the hosts are specified by name in the /etc/exports file of the NFS server, the name of the client must be written *exactly* as the NFS server sees it.

- Has someone done something on the NFS server host? Edited /etc/exports? (Maybe introduced a typo?) Run "exportfs -a"? Rebooted the server?

- Anything interesting in the syslogs, either on the NFS server or on the client? Does "dmesg" show anything that might be related?

- If you can, temporarily umount all NFS mounts from the client and run the following commands on the NFS client host:

sh /sbin/init.d/nfs.client stop
sh /sbin/init.d/nfs.core stop
sh /sbin/init.d/nfs.core start
sh /sbin/init.d/nfs.client start

This should reset as much of the NFS client subsystem as possible (the kernel components might hold some state information until the next reboot).

[Peter Nikitka]

Hi,

in addition to Matti's suggestions:
- call
showmount -e 192.191.191.202
from the HP host and compare the entries.
- check if 192.191.191.202 has really mounted something under /efsd13 .

mfG Peter

[Brecht De Baets]

Thanks for the replies,

The problem was that the NFS server host was rebooted and there was a line missing in the
exports-file.
I have addes the line and issued an 'exportfs -a' statement.

That solved my problem !