From: Perceval Anichini <perceval.anichini@laposte.net>
Subject: NFS : open is failing too slowly...
Date: 23 Jan 2004 10:58:46 +0100
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <1074851927.599.176.camel@ambre>
Mime-Version: 1.0
Content-Type: text/plain
To: nfs@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

  Hello !

Here is my problem :
	I have an application which job is to record an ip stream on a
NFS server. If the write () fails, the application continue to record
on a local disk.

	When the application is recording to the local disk, it stills
have to check wether or not the main filesystem is back. To perform
that operation, I try to open () a file on the main filesystem
regularly.

  My problem is that open () is taking far too much time to fail
(~0.3s) which lead the application to loose datas.

So my question is : Is their a fast way to know (ioctl, or whatever) if
a nfs server is available or in timeout mode ?

For infos : I am running redhat 9.0 with a kernel 2.6.1 compiled
	   "by hand"
	The filesystem is mounted with options nfsvers=3 soft timeo=1 retrans=1

	(Soft mode because I don't want my process to hang when the
server is stuck, and timeo,retrans = 1 in order to reduce the timeout
as much as possible. Tell me if i'm wrong...)

	Thanks a lot !

Perceval Anichini.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs