Re: automatic freeing of space on ENOSPC

Chuck Lever III
2021-06-29T18:39:59Z

> On Jun 29, 2021, at 2:32 PM, bfields@fieldses.org wrote:
>
> On Tue, Jun 29, 2021 at 11:43:45AM +1000, NeilBrown wrote:
>> I wonder how important this is. If an NFS client unlinks a file that it
>> has open, it will be silly_renamed, and if the client then goes silent,
>> it might never be removed. So we already theoretically have a
>> possibilty of ENOSPC due to silent clients. Have we heard of this
>> becoming a problem?
>
> Oh, that's a good point. I've seen complaints about sillyrename files,
> but I can't recall ever seen a single complaint about their causing
> ENOSPC.
>
>> Is there reason to think that the Courteous server changes will make
>> this problem more likely?
>
> So I guess the only new cases the courteous server will introduce are
> even less likely (probably just the case where a file is unlinked by a
> client other than the one that has it open).
>
> So I think doing nothing for now is an acceptable alternative....

I'm comfortable with that too. We can keep a careful eye on this
as the courteous server moves further along.

--
Chuck Lever