NFSv4 client's BUG?

Daniel Ellard ellard at netapp.com
Tue Jul 1 20:52:28 EDT 2008


Wei Yongjun wrote:
> Ellard, Daniel wrote:
>> You're never closing filedes[i], and eventually you're running out of
>> file descriptors.
>>
>> Add
>>     close(filedes[i]);
>>
>> After
>>
>>     write(filedes[i], "...
>>   
> 
> This is not the problem. Because I used ulimit -n 5000 to let program 
> can open 5000 files.

Well, it's *a* problem, even if it's not *the* problem.

Another candidate: writing 23 bytes when there are only 11 bytes in the 
string.  Probably wouldn't cause this, but who knows.

Randomness is worrisome.  Let's see if we can narrow things down at all:

- What happens when you run this on a local file system?  Same thing?

- Are you cleaning out the directory every time, or are you beginning 
each run with an arbitrary number of temp files left over from before? 
(maybe mkstemp is confused by large numbers of files in its space)  Does 
cleaning out the directory make the program break in a predictable manner?

-Dan


More information about the NFSv4 mailing list