Ignite error: Could not NFS mount

[dictum9]

I went over my configuration files time and again, and all looks good, the right directories are getting exported, etc. Both client and server are 11.23. What could be the problem?


-----------------------------------------------
ERROR: nfs mount: mount_nfs: mount: /var/opt/ignite/recovery/client_mnt:
Device busy
ERROR: Could not NFS mount directory /var/opt/ignite/clients on
sba1. The
exports file on sba1 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that
/var/opt/ignite/clients
has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory
/var/opt/ignite/recovery/client_mnt:/Error 0
(errno = 0)
ERROR: Failed to create NFS mount directories for configuration
files.
--------------------------------------------------

# cat /etc/exports
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/bcadev1 -anon=2
#
#
#
# exportfs -av
re-exported /var/opt/ignite/clients
re-exported /var/opt/ignite/recovery/archives/bcadev1
#
#
#
# cat /etc/mnttab | grep ignite
/dev/vg00/lvol9 /var/opt/ignite vxfs ioerror=mwdisable,delaylog,dev=40000009 0 0 1158271

[IT_2007 · Accepted solution]

check syslog and dmesg and it seems you have permission problem /var/opt/ignite directory.

It doesn't have write enabled permissions.

[Sandy Chen]

Hi,

You should try to restart your nfs daemon?


regards,
Sandy

[dictum9]

Program completed successfully.
ERROR: nfs mount: mount_nfs: mount: /var/opt/ignite/recovery/client_mnt:
Device busy

What does this mean, busy??

ERROR: Could not NFS mount directory /var/opt/ignite/clients on
sba1. The
exports file on sba1 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that
/var/opt/ignite/clients
has been exported using the "exportfs -av" command.

Both done...

# cat /etc/exports
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/bcadev1 -anon=2

# exportfs -av
re-exported /var/opt/ignite/clients
re-exported /var/opt/ignite/recovery/archives/bcadev1
#




ERROR: Failed mounting directory
/var/opt/ignite/recovery/client_mnt:/Error 0
(errno = 0)
ERROR: Failed to create NFS mount directories for configuration
files.


What does it mean?

Also I restarted the NFS daemons many times, even rebooted the machine.


sbin/init.d# ./nfs.client stop
killing biod
killing automountd
sbin/init.d# ./nfs.server stop
killing rpc.lockd
killing rpc.statd
killing rpc.pcnfsd
killing nfsd
killing rpc.mountd
sbin/init.d# ./nfs.core stop
stopping rpcbind
sbin/init.d# ./nfs.core start
starting NFS CORE networking

starting up the rpcbind
/usr/sbin/rpcbind
sbin/init.d# ./nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 16835
Reading in /etc/exports
starting up the mount daemon
/usr/sbin/rpc.mountd
starting up the NFS daemons
/usr/sbin/nfsd 16
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
tarting up the PC-NFS daemon
/usr/sbin/rpc.pcnfsd
sbin/init.d# ./nfs.client start
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 16835
starting up the BIO daemons
/usr/sbin/biod 16
Reading in /etc/exports
starting up the Status Monitor daemon
rpc.statd already started, using pid: 16882
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 16894
Starting up the AutoFS daemon
/usr/sbin/automountd
Running the AutoFS command interface
/usr/sbin/automount
mounting remote NFS file systems ...
mounting CacheFS file systems ...


# rpcinfo -p | grep nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
150001 1 udp 964 pcnfsd
150001 2 udp 964 pcnfsd
150001 1 tcp 965 pcnfsd
150001 2 tcp 965 pcnfsd
#

[Ivan Krastev]

Can you try on client :
mount server:/var/opt/ignite/clients /tmp/test

and see whats happening ?

regards,
ivan

[dictum9]

It mounts just fine.

[Jeff Kalchik]

I ran across this issue recently here.

It mounted successfully at another mountpoint, but failed at /var/opt/ignite/recovery/client_mnt. The reason it failed was a left over NFS mount from an earlier run of make_net_recovery to another server. When make_net_recovery run, it makes 2 NFS mounts, but one of them is left around after execution completes. (Ignite/UX C.6.8.152)

Check all of your existing mounts through 'showmount -a', 'mount', /etc/mnttab, etc. on the client system.

[dictum9]

And that hit the nail squarely on the head.
I forgot I was using another server before I switched over to this one. There was nothing wrong with the Ignite server configuration, but the client had the previously mounted filesystem, and once I unmounted it, all was fine.