nfs mount: get_fh: server1:: RPC: Program not registered

[R.O.]

Hi all,

I have two UX 11.0 servers. server1 exports a directory and server2 mount it. Sometimes, due to a power outage, the two servers reboot. Server2 reboots faster than server1, so when server2 try to mount the directory exported by server1, the nfs daemons are not yet running on server1 and I can see this in /etc/rc.log of server2:
Start NFS client subsystem
Output from "/sbin/rc2.d/S430nfs.client start":
----------------------------
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 744
starting up the BIO daemons
/usr/sbin/biod 4
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
mounting remote NFS file systems ...
nfs mount: get_fh: server1:: RPC: Program not registered
nfs mount: get_fh: server1:: RPC: Program not registered
nfs mount: retry: retrying(1) for: /data after 5 seconds
nfs mount: retry: giving up on: /data

FAILURE CODE: 1
Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

I need that server2 waits to server1 to mount this directory or try to mount it until the nfs daemons run in server1. How can I do this??

Here is the line in fstab of server2:

server2:/data /data nfs rw,suid,soft 0 0

Regards,

R.O.

[H.Merijn Brand (procura]

Though it would not be *my* choice (you run into possible lock problems and server 2 would not boot or takes ages to boot if server 1 is down) you should remove 'soft' from the mount line.

MUCH better would be to have it go to default boot level without mounting (add 'noauto' to the mount options) and start a script (from rc) with a default sleep of (say) 10 minutes and mount the server shares if not yet mounted

Enjoy, have FUN! H.Merijn

[T G Manikandan]

One of the options which can only suit your question is that changing the option from "soft" to "hard"

Hard would mean that the client is waiting for the response from the NFS server for ever.

I would not recommend the option hard as any problem with the NFS server the client stops responding so soft option is always preferred.


soft--retries the server for quite number of times and then times out.


Thanks

[Radhakrishnan Venkatara]

hi,

check this links

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xce7db47b9a27d6118ff40090279cd0f9,00.html

u can use background mode which allows filesystems to mount in background mode


http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B1031-90048/B1031-90048_top.html&con=/hpux/onlinedocs/B1031-90048/00/00/9-con.html&toc=/hpux/onlinedocs/B1031-90048/00/00/9-toc.html&searchterms=hard%20soft%20mount&queryid=20020222-073324


Specify bg for mounting directories that are not necessary for the client to boot or operate correctly. Background mounts that fail are retried in the background, allowing the mount process to consider the mount complete and go on to the next one. If you have two machines configured to mount directories from each other, configure the mounts on one of the machines as background mounts. That way, if both systems try to boot at once, they will not become deadlocked, each waiting to mount directories from the other. The bg option cannot be used with automounted directories.

hope this will be helpful.

radhakrishnan

[Radhakrishnan Venkatara]

hi,

I agree with Manikandan and merijin if u want ur server2 to wait still server1 comes up.

radhakrishnan