From: Filipe Manana <fdmanana@kernel.org>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 2/2] btrfs: reserve extra space for the free space tree
Date: Mon, 6 Dec 2021 10:44:51 +0000 [thread overview]
Message-ID: <Ya3po87VEgtlwdwD@debian9.Home> (raw)
In-Reply-To: <18b2ae0948a035aa809ba38641439e2d4167ca29.1638477127.git.josef@toxicpanda.com>
On Thu, Dec 02, 2021 at 03:34:32PM -0500, Josef Bacik wrote:
> Filipe reported a problem where sometimes he'd get an ENOSPC abort when
> running delayed refs with generic/619 and the free space tree enabled.
> This is partly because we do not reserve space for modifying the free
> space tree, nor do we have a block rsv associated with that tree.
>
> The delayed_refs_rsv tracks the amount of space required to run delayed
> refs. This means 1 modification means 1 change to the extent root.
> With the free space tree this turns into 2 changes, because modifying 1
> extent means updating the extent tree and potentially updating the free
> space tree to either remove that entry or add the free space. Thus if
> we have the FST enabled, simply double the reservation size for our
> modification.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
> fs/btrfs/block-rsv.c | 1 +
> fs/btrfs/delayed-ref.c | 22 ++++++++++++++++++++++
> 2 files changed, 23 insertions(+)
>
> diff --git a/fs/btrfs/block-rsv.c b/fs/btrfs/block-rsv.c
> index b3086f252ad0..b3ee49b0b1e8 100644
> --- a/fs/btrfs/block-rsv.c
> +++ b/fs/btrfs/block-rsv.c
> @@ -426,6 +426,7 @@ void btrfs_init_root_block_rsv(struct btrfs_root *root)
> switch (root->root_key.objectid) {
> case BTRFS_CSUM_TREE_OBJECTID:
> case BTRFS_EXTENT_TREE_OBJECTID:
> + case BTRFS_FREE_SPACE_TREE_OBJECTID:
> root->block_rsv = &fs_info->delayed_refs_rsv;
> break;
> case BTRFS_ROOT_TREE_OBJECTID:
> diff --git a/fs/btrfs/delayed-ref.c b/fs/btrfs/delayed-ref.c
> index da9d20813147..533521be8fdf 100644
> --- a/fs/btrfs/delayed-ref.c
> +++ b/fs/btrfs/delayed-ref.c
> @@ -84,6 +84,17 @@ void btrfs_delayed_refs_rsv_release(struct btrfs_fs_info *fs_info, int nr)
> u64 num_bytes = btrfs_calc_insert_metadata_size(fs_info, nr);
> u64 released = 0;
>
> + /*
> + * We have to check the mount option here because we could be enabling
> + * the free space tree for the first time and don't have the compat_ro
> + * option set yet.
> + *
> + * We need extra reservations if we have the free space tree because
> + * we'll have to modify that tree as well.
> + */
> + if (btrfs_test_opt(fs_info, FREE_SPACE_TREE))
> + num_bytes <<= 1;
> +
> released = btrfs_block_rsv_release(fs_info, block_rsv, num_bytes, NULL);
> if (released)
> trace_btrfs_space_reservation(fs_info, "delayed_refs_rsv",
> @@ -108,6 +119,17 @@ void btrfs_update_delayed_refs_rsv(struct btrfs_trans_handle *trans)
>
> num_bytes = btrfs_calc_insert_metadata_size(fs_info,
> trans->delayed_ref_updates);
> + /*
> + * We have to check the mount option here because we could be enabling
> + * the free space tree for the first time and don't have the compat_ro
> + * option set yet.
> + *
> + * We need extra reservations if we have the free space tree because
> + * we'll have to modify that tree as well.
> + */
> + if (btrfs_test_opt(fs_info, FREE_SPACE_TREE))
> + num_bytes <<= 1;
Don't we need to bump the minimum (limit variable) number of bytes at
btrfs_delayed_refs_rsv_refill() as well?
I don't see why not.
Thanks.
> +
> spin_lock(&delayed_rsv->lock);
> delayed_rsv->size += num_bytes;
> delayed_rsv->full = 0;
> --
> 2.26.3
>
next prev parent reply other threads:[~2021-12-06 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 20:34 [PATCH v2 0/2] Free space tree space reservation fixes Josef Bacik
2021-12-02 20:34 ` [PATCH v2 1/2] btrfs: include the free space tree in the global rsv minimum calculation Josef Bacik
2021-12-02 20:34 ` [PATCH v2 2/2] btrfs: reserve extra space for the free space tree Josef Bacik
2021-12-06 10:44 ` Filipe Manana [this message]
2021-12-06 19:43 ` Josef Bacik
2021-12-03 13:09 ` [PATCH v2 0/2] Free space tree space reservation fixes Nikolay Borisov
2021-12-06 10:42 ` Filipe Manana
2021-12-06 19:54 ` Josef Bacik
2021-12-07 18:59 ` David Sterba
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=Ya3po87VEgtlwdwD@debian9.Home \
--to=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.