From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/6] xfs: try harder to reclaim space when we run out
Date: Tue, 31 Dec 2019 17:07:13 -0800 [thread overview]
Message-ID: <157784083298.1361522.7064886067520069080.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 been hanging onto 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.
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
next reply other threads:[~2020-01-01 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 1:07 Darrick J. Wong [this message]
2020-01-01 1:07 ` [PATCH 1/6] xfs: refactor messy xfs_inode_free_quota_* functions Darrick J. Wong
2020-01-01 1:07 ` [PATCH 2/6] xfs: don't stall cowblocks scan if we can't take locks Darrick J. Wong
2020-01-01 1:07 ` [PATCH 3/6] xfs: move inode flush to a workqueue Darrick J. Wong
2020-01-01 1:07 ` [PATCH 4/6] xfs: xfs_inode_free_quota_blocks should scan project quota Darrick J. Wong
2020-01-01 1:07 ` [PATCH 5/6] xfs: flush speculative space allocations when we run out of quota Darrick J. Wong
2020-01-01 1:07 ` [PATCH 6/6] 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=157784083298.1361522.7064886067520069080.stgit@magnolia \
--to=darrick.wong@oracle.com \
--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).