NFS and fseek.

[Alan Ennen]

We are running on a 64 way HP, B.11.23 U ia64.

We are looking at NAS files systems for some of our storage and have encountered some recent odd behavior in testing.

Issue: fseek randomly fails due to file not found error where temp file being created and used is on the NAS file system. File is present.

Code runs fine on a SAN mounted file system.

Wonder if anyone has heard of this type of issue related to NFS.

[Dennis Handly]

>fseek randomly fails due to file not found error where temp file being created and used is on the NAS file system.

That error should only appear on the open(2), not fseek(3). How are you detecting the fseek error?

Are you first checking the fseek return value for -1?

[Alan Ennen]

code first checks for -1 return from fseek then prints sterror(errno);

[Dennis Handly]

>code first checks for -1 return from fseek then prints sterror(errno);

That seems correct.
Is this a threaded application? Are you including ?