From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: NeilBrown <neilb@suse.de>,
Trond Myklebust <trondmy@hammerspace.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"dai.ngo@oracle.com" <dai.ngo@oracle.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: automatic freeing of space on ENOSPC
Date: Tue, 29 Jun 2021 14:34:54 -0400 [thread overview]
Message-ID: <20210629183454.GB1926@fieldses.org> (raw)
In-Reply-To: <CAOQ4uxj-YLrsvCE1d8+OEYQpfZeENK71OWR02G3JtLoZx92H1g@mail.gmail.com>
On Tue, Jun 29, 2021 at 07:07:47AM +0300, Amir Goldstein wrote:
> To me, stale silly renamed files sounds like a problem worth fixing
> not as an excuse to create another similar problem.
Yeah, it's ugly, I'd like to fix it some day, but given that people have
lived with it since forever it's not the highest priority.
> w.r.t pre-ENOSPC notification, I don't know of such notification
> in filesystems. It exists for some thin-provisioned storage devices
> (thinp as well I think), but that is not very useful for nfsd.
>
> OTOH, ENOSPC is rarely a surprising event.
> I believe you can get away with tunable for nfsd, such as
> % of available storage space that may consumed for
> "opportunistic caching".
>
> Polling for available storage space every least time or so
> in case there are possibly forgotten unlinked files should be
> sufficient for any practical purpose IMO.
Makes sense, thanks for the perspective.
--b.
next prev parent reply other threads:[~2021-06-29 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 19:49 automatic freeing of space on ENOSPC J. Bruce Fields
2021-06-29 0:43 ` Trond Myklebust
2021-06-29 1:12 ` bfields
2021-06-29 1:43 ` NeilBrown
2021-06-29 4:07 ` Amir Goldstein
2021-06-29 18:34 ` bfields [this message]
2021-06-29 18:32 ` bfields
2021-06-29 18:39 ` Chuck Lever III
2021-06-29 5:11 ` Dave Chinner
2021-06-29 18:37 ` J. Bruce Fields
2021-06-29 16:47 ` Theodore Ts'o
2021-06-29 18:38 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210629183454.GB1926@fieldses.org \
--to=bfields@fieldses.org \
--cc=amir73il@gmail.com \
--cc=dai.ngo@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trondmy@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).