NFS on TCP4.25

I have encountered a problem when I started using NFS. If I mount a remote
filesystem, for example:

mount_nfs host_a:/ /nfs_A

all works fine. I can access the remote filesystem as /nfs_A/…

If the connection to host_a gets disconnected, any file access to /nfs_A
hangs the program indefinately. I have even tried to set an alarm timer
ahead of my fopen(), and it still doesn’t return.

Has anyone else experienced this, and what kind of work-around is there? I
am currently using TCP 4.25C.

Thanks,

Jeff Adler
Automation Services

“Jeffrey Adler” <jeffadler.at.bigfoot.dot.com@nowhere.com> wrote in message
news:crecfk$c24$1@inn.qnx.com

I have encountered a problem when I started using NFS. If I mount a remote
filesystem, for example:

mount_nfs host_a:/ /nfs_A

all works fine. I can access the remote filesystem as /nfs_A/…

If the connection to host_a gets disconnected, any file access to /nfs_A
hangs the program indefinately. I have even tried to set an alarm timer
ahead of my fopen(), and it still doesn’t return.

Has anyone else experienced this, and what kind of work-around is there?
I am currently using TCP 4.25C.

Don’t know if this will make a difference but TCP 4.25 nfs is know to be
badly broken. TCP 5.0 is, i’m told, better at doing NFS

Thanks,

Jeff Adler
Automation Services
\

I have had similar experience. On LAN disconnect, ls /, ls /nfs_mountpoint
and ping xxx all hang indefinately and do not recover on reconnect of the
LAN - only way out is to ^C. This makes connection integrity checking very
difficult.

Jeff, it appears that you may have since upgraded to TCP/IP 5.0. Did this
upgrade make things better?

Gord

“Gord Sipko” <mountkidd_AT_shaw_DOT_ca@nospam.com> wrote in message
news:ct30sd$2k2$2@inn.qnx.com

I have had similar experience. On LAN disconnect, ls /, ls /nfs_mountpoint
and ping xxx all hang indefinately and do not recover on reconnect of the
LAN - only way out is to ^C. This makes connection integrity checking very
difficult.

Jeff, it appears that you may have since upgraded to TCP/IP 5.0. Did this
upgrade make things better?

Gord

Yes, I did upgrade. I am not sure if things are better or not.

I took the recommendations of the newsgroup folk that TCP/IP 5.0 is better
than 4.25D. I’m not convinced that they either one is normally
“trouble-free”. I hope that 5.0 is less troublesome, but I don’t have the
opportunity to compare one over the other.

Jeff.

Thanks for the reply Jeff! I was hoping for reassurance that TCPIP 5.0 is
leaps and bounds above 4.25. I guess I’ll just make the best best of what I
now have…

Gord