From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org
Subject: [PATCHSET v3 00/11] xfs: try harder to reclaim space when we run out
Date: Mon, 18 Jan 2021 14:11:58 -0800 [thread overview]
Message-ID: <161100791789.88816.10902093186807310995.stgit@magnolia> (raw)
Hi all,
Historically, when users ran out of space or quota when trying to write
to the filesystem, XFS didn't try very hard to reclaim space that it
might have speculatively allocated for the purpose of speeding up
front-end filesystem operations (appending writes, cow staging). The
upcoming deferred inactivation series will greatly increase the amount
of allocated space that isn't actively being used to store user data.
Therefore, try to reduce the circumstances where we return EDQUOT or
ENOSPC to userspace by teaching the write paths to try to clear space
and retry the operation one time before giving up.
v2: clean up and rebase against 5.11.
v3: restructure the retry loops per dchinner suggestion
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=reclaim-space-harder-5.12
---
fs/xfs/libxfs/xfs_attr.c | 10 ++
fs/xfs/libxfs/xfs_bmap.c | 10 ++
fs/xfs/xfs_bmap_util.c | 22 +++--
fs/xfs/xfs_file.c | 26 ++++--
fs/xfs/xfs_icache.c | 189 +++++++++++++++++++++++++++++++---------------
fs/xfs/xfs_icache.h | 9 ++
fs/xfs/xfs_inode.c | 22 ++++-
fs/xfs/xfs_ioctl.c | 18 +++-
fs/xfs/xfs_iomap.c | 24 ++++--
fs/xfs/xfs_iops.c | 20 +++--
fs/xfs/xfs_qm.c | 36 +++++++--
fs/xfs/xfs_quota.h | 36 +++++----
fs/xfs/xfs_reflink.c | 31 +++++---
fs/xfs/xfs_symlink.c | 12 ++-
fs/xfs/xfs_trace.c | 1
fs/xfs/xfs_trace.h | 40 ++++++++++
fs/xfs/xfs_trans.c | 20 +++++
fs/xfs/xfs_trans_dquot.c | 108 +++++++++++++++++++++++---
18 files changed, 466 insertions(+), 168 deletions(-)
next reply other threads:[~2021-01-18 22:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 22:11 Darrick J. Wong [this message]
2021-01-18 22:12 ` [PATCH 01/11] xfs: refactor messy xfs_inode_free_quota_* functions Darrick J. Wong
2021-01-18 22:12 ` [PATCH 02/11] xfs: don't stall cowblocks scan if we can't take locks Darrick J. Wong
2021-01-19 6:49 ` Christoph Hellwig
2021-01-18 22:12 ` [PATCH 03/11] xfs: xfs_inode_free_quota_blocks should scan project quota Darrick J. Wong
2021-01-18 22:12 ` [PATCH 04/11] xfs: move and rename xfs_inode_free_quota_blocks to avoid conflicts Darrick J. Wong
2021-01-19 6:53 ` Christoph Hellwig
2021-01-18 22:12 ` [PATCH 05/11] xfs: pass flags and return gc errors from xfs_blockgc_free_quota Darrick J. Wong
2021-01-19 6:59 ` Christoph Hellwig
2021-01-18 22:12 ` [PATCH 06/11] xfs: flush eof/cowblocks if we can't reserve quota for file blocks Darrick J. Wong
2021-01-19 3:56 ` Darrick J. Wong
2021-01-19 7:08 ` Christoph Hellwig
2021-01-19 19:43 ` Darrick J. Wong
2021-01-18 22:12 ` [PATCH 07/11] xfs: flush eof/cowblocks if we can't reserve quota for inode creation Darrick J. Wong
2021-01-18 22:12 ` [PATCH 08/11] xfs: flush eof/cowblocks if we can't reserve quota for chown Darrick J. Wong
2021-01-18 22:12 ` [PATCH 09/11] xfs: add a tracepoint for blockgc scans Darrick J. Wong
2021-01-19 7:11 ` Christoph Hellwig
2021-01-18 22:12 ` [PATCH 10/11] xfs: refactor xfs_icache_free_{eof,cow}blocks call sites Darrick J. Wong
2021-01-18 22:12 ` [PATCH 11/11] xfs: flush speculative space allocations when we run out of space Darrick J. Wong
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=161100791789.88816.10902093186807310995.stgit@magnolia \
--to=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
/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).