From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: reflink should force the log out if mounted with wsync
Date: Fri, 3 Apr 2020 08:55:49 +1100 [thread overview]
Message-ID: <20200402215549.GB21885@dread.disaster.area> (raw)
In-Reply-To: <20200402041705.GD80283@magnolia>
On Wed, Apr 01, 2020 at 09:17:05PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Reflink should force the log out to disk if the filesystem was mounted
> with wsync, the same as most other operations in xfs.
>
> Fixes: 3fc9f5e409319 ("xfs: remove xfs_reflink_remap_range")
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/xfs_file.c | 21 +++++++++++++++++++--
> fs/xfs/xfs_reflink.c | 15 ++++++++++++++-
> fs/xfs/xfs_reflink.h | 3 ++-
> 3 files changed, 35 insertions(+), 4 deletions(-)
>
> diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> index b8a4a3f29b36..17bdc5bbc2ae 100644
> --- a/fs/xfs/xfs_file.c
> +++ b/fs/xfs/xfs_file.c
> @@ -1029,8 +1029,10 @@ xfs_file_remap_range(
> struct inode *inode_out = file_inode(file_out);
> struct xfs_inode *dest = XFS_I(inode_out);
> struct xfs_mount *mp = src->i_mount;
> + xfs_lsn_t sync_lsn = 0;
> loff_t remapped = 0;
> xfs_extlen_t cowextsize;
> + bool need_sync;
> int ret;
>
> if (remap_flags & ~(REMAP_FILE_DEDUP | REMAP_FILE_ADVISORY))
> @@ -1068,13 +1070,28 @@ xfs_file_remap_range(
> cowextsize = src->i_d.di_cowextsize;
>
> ret = xfs_reflink_update_dest(dest, pos_out + len, cowextsize,
> - remap_flags);
> + remap_flags, &need_sync);
> + if (ret)
> + goto out_unlock;
> +
> + /*
> + * If this is a synchronous mount and xfs_reflink_update_dest didn't
> + * already take care of this, make sure that the transaction goes to
> + * disk before returning to the user.
> + */
> + if (need_sync && xfs_ipincount(dest))
> + sync_lsn = dest->i_itemp->ili_last_lsn;
>
> out_unlock:
> xfs_reflink_remap_unlock(file_in, file_out);
> if (ret)
> trace_xfs_reflink_remap_range_error(dest, ret, _RET_IP_);
> - return remapped > 0 ? remapped : ret;
> + if (remapped > 0) {
> + if (sync_lsn)
> + xfs_log_force_lsn(mp, sync_lsn, XFS_LOG_SYNC, NULL);
> + return remapped;
> + }
> + return ret;
This seems pretty fragile compared to all the other WSYNC cases
which just set the last transaction as a sync transaction.
Why can't we just set the transaction sync at the appropriate time,
and if we have to do two sync commits for a reflink then we just
suck it up for now?
As it is, wsync is really only used for active/passive HA configs
these days, which means we've already given up on performance
because data integrity is an essential requirement in those
configs...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2020-04-02 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 4:17 [PATCH] xfs: reflink should force the log out if mounted with wsync Darrick J. Wong
2020-04-02 7:51 ` Christoph Hellwig
2020-04-02 8:49 ` Christoph Hellwig
2020-04-02 14:53 ` Darrick J. Wong
2020-04-02 14:56 ` Christoph Hellwig
2020-04-02 15:14 ` Darrick J. Wong
2020-04-02 15:20 ` Christoph Hellwig
2020-04-02 21:55 ` Dave Chinner [this message]
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=20200402215549.GB21885@dread.disaster.area \
--to=david@fromorbit.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