NFSv4 client's BUG?

[J. Bruce Fields]

On Wed, Jul 02, 2008 at 09:55:16AM +0800, Wei Yongjun wrote:
> J. Bruce Fields wrote:
>> On Wed, Jul 02, 2008 at 08:39:16AM +0800, 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.
>>> The "fopen: Input/output error" may happend when I just open 40 
>>> files, it is random.
>>>     
>>
>> What's the server?  Could you watch the traffic in wireshark and see
>> whether the server is returning an error on the failing open?
>>   
>
> I have tcpdump the packets, there is no error return by the server.

Does tcpdump ever tell you about nfsv4 errors?  I'm not sure it actually
knows where to look for the nfsv4 status.

Wireshark would be more helpful.

--b.