Skip to contentSkip to conversation

NFS : open is failing too slowly...

DISCUSSION Perceval Anichini 1 participant 1 message Jan 23, 2004

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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 - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs