From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/3] xfs: use deferred frees to reap old btree blocks
Date: Thu, 17 Oct 2019 08:55:37 -0400 [thread overview]
Message-ID: <20191017125537.GE20114@bfoster> (raw)
In-Reply-To: <157063973378.2913192.158267929318422892.stgit@magnolia>
On Wed, Oct 09, 2019 at 09:48:53AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Use deferred frees (EFIs) to reap the blocks of a btree that we just
> replaced. This helps us to shrink the window in which those old blocks
> could be lost due to a system crash, though we try to flush the EFIs
> every few hundred blocks so that we don't also overflow the transaction
> reservations during and after we commit the new btree.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/scrub/repair.c | 29 ++++++++++++++++++++++++-----
> 1 file changed, 24 insertions(+), 5 deletions(-)
>
>
> diff --git a/fs/xfs/scrub/repair.c b/fs/xfs/scrub/repair.c
> index e21faef6db5a..8349694f985d 100644
> --- a/fs/xfs/scrub/repair.c
> +++ b/fs/xfs/scrub/repair.c
...
> @@ -565,14 +568,24 @@ xrep_reap_block(
> xrep_reap_invalidate_block(sc, fsbno);
> error = xrep_put_freelist(sc, agbno);
> } else {
> + /*
> + * Use deferred frees to get rid of the old btree blocks to try
> + * to minimize the window in which we could crash and lose the
> + * old blocks. However, we still need to roll the transaction
> + * every 100 or so EFIs so that we don't exceed the log
> + * reservation.
> + */
> xrep_reap_invalidate_block(sc, fsbno);
> - error = xfs_free_extent(sc->tp, fsbno, 1, oinfo, resv);
> + __xfs_bmap_add_free(sc->tp, fsbno, 1, oinfo, true);
xfs_free_extent() sets skip_discard to false and this changes it to
true. Intentional?
Otherwise the rest looks straightforward.
Brian
> + (*deferred)++;
> + need_roll = *deferred > 100;
> }
> if (agf_bp != sc->sa.agf_bp)
> xfs_trans_brelse(sc->tp, agf_bp);
> - if (error)
> + if (error || !need_roll)
> return error;
>
> + *deferred = 0;
> if (sc->ip)
> return xfs_trans_roll_inode(&sc->tp, sc->ip);
> return xrep_roll_ag_trans(sc);
> @@ -594,6 +607,7 @@ xrep_reap_extents(
> struct xfs_bitmap_range *bmr;
> struct xfs_bitmap_range *n;
> xfs_fsblock_t fsbno;
> + unsigned int deferred = 0;
> int error = 0;
>
> ASSERT(xfs_sb_version_hasrmapbt(&sc->mp->m_sb));
> @@ -605,12 +619,17 @@ xrep_reap_extents(
> XFS_FSB_TO_AGNO(sc->mp, fsbno),
> XFS_FSB_TO_AGBNO(sc->mp, fsbno), 1);
>
> - error = xrep_reap_block(sc, fsbno, oinfo, type);
> + error = xrep_reap_block(sc, fsbno, oinfo, type, &deferred);
> if (error)
> break;
> }
>
> - return error;
> + if (error || deferred == 0)
> + return error;
> +
> + if (sc->ip)
> + return xfs_trans_roll_inode(&sc->tp, sc->ip);
> + return xrep_roll_ag_trans(sc);
> }
>
> /*
>
next prev parent reply other threads:[~2019-10-17 12:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 16:48 [PATCH 0/3] xfs: fix online repair block reaping Darrick J. Wong
2019-10-09 16:48 ` [PATCH 1/3] xfs: xrep_reap_extents should not destroy the bitmap Darrick J. Wong
2019-10-17 12:54 ` Brian Foster
2019-10-09 16:48 ` [PATCH 2/3] xfs: only invalidate blocks if we're going to free them Darrick J. Wong
2019-10-17 12:55 ` Brian Foster
2019-10-25 20:22 ` Darrick J. Wong
2019-10-09 16:48 ` [PATCH 3/3] xfs: use deferred frees to reap old btree blocks Darrick J. Wong
2019-10-17 12:55 ` Brian Foster [this message]
2019-10-17 15:06 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 23:30 [PATCH v2 0/3] xfs: fix online repair block reaping Darrick J. Wong
2019-10-29 23:30 ` [PATCH 3/3] xfs: use deferred frees to reap old btree blocks Darrick J. Wong
2020-01-01 1:01 [PATCH v2 0/3] xfs: fix online repair block reaping Darrick J. Wong
2020-01-01 1:01 ` [PATCH 3/3] xfs: use deferred frees to reap old btree blocks 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=20191017125537.GE20114@bfoster \
--to=bfoster@redhat.com \
--cc=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).