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

Re: automatic freeing of space on ENOSPC

From: NeilBrown <hidden>
Date: 2021-06-29 01:43:52
Also in: linux-fsdevel

On Tue, 29 Jun 2021, bfields@fieldses.org wrote:
On Tue, Jun 29, 2021 at 12:43:14AM +0000, Trond Myklebust wrote:
quoted
How about just setting up a notification for unlink on those files, the
same way we set up notifications for close with the NFSv3 filecache in
nfsd?
Yes, that'd probably work.  It'd be better if we didn't have to throw
away unlinked files when the client expires, but it'd still be an
incremental improvement over what we do now.
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?
Is there reason to think that the Courteous server changes will make
this problem more likely? 

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