Re: NFSERR_NOSPC nfs-client bug

[Greg Banks <gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>]

Trond Myklebust wrote:
> On Tue, 2008-03-18 at 13:08 +1100, Greg Banks wrote:
>   
>> Ray Ferguson wrote:
>>     
>>> On Monday 17 March 2008 20:43, Greg Banks wrote:
>>>   
>>>       
>>>> It doesn't ignore ENOSPC, it reports it on close().  Of course this is
>>>> often several gigabytes of lost data too late.
>>>>     
>>>>         
>>> In our case, the thrashing it gave our Linux NFS cluster was severe enough to  
>>> take it out of commission.  The lost data from the file transfer that 
>>> triggered the event was the least of our worries.
>>>
>>>   
>>>       
>> Agreed, it sucks.
>>     
>
> Try a more recent kernel: 2.6.24 and more recent will report these
> errors more promptly.
>   
So that would be
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7b159fc18d417980f57aef64cab3417ee6af70f8

?
Is my reading right, that a solitary transient ENOSPC is still reported
at close(), but a sequence of two or more ENOSPC is reported in the next
write() call?

-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
The cake is *not* a lie.
I don't speak for SGI.