Re: Giving up an NFS fs that wasn't available initially?

From: Oron Peled (oron_at_nonexisting.hamakor.org.il)
Date: Tue 25 May 2004 - 02:24:02 IDT


On Tuesday 25 May 2004 00:55, Shaul Karl wrote:
> Shouldn't an NFS client retry to mount a fs that wasn't available when
> the client boot? In other words, if the NFS server was not available
> when the client boots, shouldn't the client retry to mount the fs
> according to the retry parameter?

Depends on the mount options. See below.

> The client attempt to mount the remote fs bg,soft,intr.

From the mount(8) man page:
  soft This option allows the kernel to time out if the nfs server is
         not responding for some time. The time can be specified with
         timeo=time. This option might be useful if your nfs server
         sometimes doesn't respond or will be rebooted while some process
         tries to get a file from the server. Usually it just causes
         lots of trouble.

However, please note that the complement option (hard) will cause your
NFS client to retry forever (unless you send it SIGINT -- you specified
the 'intr' option as well). This of course may cause problems in different
situations.

Your tradeoff, your call.

-- 
Oron Peled                             Voice/Fax: +972-4-8228492
oron_at_actcom.co.il                  http://www.actcom.co.il/~oron
"Normal people ... believe that if it ain't broke, don't fix it.
Engineers believe that if it ain't broke, it doesn't have enough
features ... yet." -- Scott Adams
=================================================================
To unsubscribe, send mail to linux-il-request_at_linux.org.il with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail linux-il-request_at_linux.org.il


This archive was generated by hypermail 2.1.7 : Tue 25 May 2004 - 02:36:48 IDT