Thread (12 messages) 12 messages, 7 authors, 2021-06-29

Re: automatic freeing of space on ENOSPC

From: bfields@fieldses.org <hidden>
Date: 2021-06-29 18:33:00
Also in: linux-fsdevel

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....

--b.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help