linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Filipe David Borba Manana <fdmanana@gmail.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] xfstests: add test for btrfs clone + fsync durability
Date: Tue, 10 Jun 2014 12:10:17 +1000	[thread overview]
Message-ID: <20140610021017.GL4453@dastard> (raw)
In-Reply-To: <1402282132-618-1-git-send-email-fdmanana@gmail.com>

On Mon, Jun 09, 2014 at 03:48:52AM +0100, Filipe David Borba Manana wrote:
> Regression test for btrfs ioctl clone operation + fsync + log
> recovery. The issue was that doing an fsync after cloning into
> a file didn't gave any persistence guarantees as it should.
> What happened was that the in memory metadata (extent maps)
> weren't updated, which made the fsync code not able to detect
> that file data has been changed and must be persisted to the
> log.
> 
> This issue is fixed by the following linux kernel btrfs patch:
> 
>     Btrfs: make fsync work after cloning into a file
> 
> Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
> ---
> 
> V2: Test small files too, consisting of a single inline extent, as
>     it triggers different code paths.
> 
>  tests/btrfs/056     | 150 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  tests/btrfs/056.out | 129 ++++++++++++++++++++++++++++++++++++++++++++
>  tests/btrfs/group   |   1 +
>  3 files changed, 280 insertions(+)
>  create mode 100755 tests/btrfs/056
>  create mode 100644 tests/btrfs/056.out
> 
> diff --git a/tests/btrfs/056 b/tests/btrfs/056
> new file mode 100755
> index 0000000..e066442
> --- /dev/null
> +++ b/tests/btrfs/056
> @@ -0,0 +1,150 @@
> +#! /bin/bash
> +# FS QA Test No. btrfs/056
> +#
> +# Regression test for btrfs ioctl clone operation + fsync + log recovery.
> +# The issue was that doing an fsync after cloning into a file didn't gave any
> +# persistence guarantees as it should. What happened was that the in memory
> +# metadata (extent maps) weren't updated, which made the fsync code not able
> +# to detect that file data has been changed.
> +#
> +# This issue is fixed by the following linux kernel btrfs patch:
> +#
> +#    Btrfs: make fsync work after cloning into a file
> +#
> +#-----------------------------------------------------------------------
> +# Copyright (c) 2014 Filipe Manana.  All Rights Reserved.
> +#
> +# This program is free software; you can redistribute it and/or
> +# modify it under the terms of the GNU General Public License as
> +# published by the Free Software Foundation.
> +#
> +# This program is distributed in the hope that it would be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program; if not, write the Free Software Foundation,
> +# Inc.,  51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
> +#-----------------------------------------------------------------------
> +#
> +
> +seq=`basename $0`
> +seqres=$RESULT_DIR/$seq
> +echo "QA output created by $seq"
> +
> +tmp=/tmp/$$
> +status=1	# failure is the default!
> +trap "_cleanup; exit \$status" 0 1 2 3 15
> +
> +_cleanup()
> +{
> +	_cleanup_flakey
> +	rm -fr $tmp
> +}
> +
> +# get standard environment, filters and checks
> +. ./common/rc
> +. ./common/filter
> +. ./common/dmflakey
> +
> +# real QA test starts here
> +_supported_fs btrfs
> +_supported_os Linux
> +_require_scratch
> +_require_btrfs_cloner
> +_require_btrfs_fs_feature "no_holes"
> +_require_btrfs_mkfs_feature "no-holes"
> +_require_dm_flakey
> +_need_to_be_root
> +
> +rm -f $seqres.full
> +
> +test_btrfs_clone_fsync_log_recover()
> +{
> +	_scratch_mkfs "$1" >/dev/null 2>&1
> +	_init_flakey
> +	SAVE_MOUNT_OPTIONS="$MOUNT_OPTIONS"
> +	MOUNT_OPTIONS="$MOUNT_OPTIONS $2"
> +	_mount_flakey
> +
> +	# Create a file with 4 extents and 1 hole, all with a size of 8Kb each.
> +	# The hole is in the range [16384, 24576[.
> +	$XFS_IO_PROG -f -c "pwrite -S 0x01 -b 8192 0 8192" \
> +			-c "fsync" \
> +			-c "pwrite -S 0x02 -b 8192 8192 8192" \
> +			-c "fsync" \
> +			-c "pwrite -S 0x04 -b 8192 24576 8192" \
> +			-c "fsync" \
> +			-c "pwrite -S 0x05 -b 8192 32768 8192" \
> +			-c "fsync" \
> +		$SCRATCH_MNT/foo | _filter_xfs_io
> +
> +	# Clone destination file, 1 extent of 96kb.
> +	$XFS_IO_PROG -f -c "pwrite -S 0xff -b 98304 0 98304" -c "fsync" \
> +		$SCRATCH_MNT/bar | _filter_xfs_io

I've seen this pattern before ;)

Use the "-s" option to xfs_io rather than repeated "pwrite/fsync"
pairs.

Otherwise looks fine.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2014-06-10  2:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  4:08 [PATCH] xfstests: add test for btrfs clone + fsync durability Filipe David Borba Manana
2014-06-09  2:48 ` [PATCH v2] " Filipe David Borba Manana
2014-06-10  2:10   ` Dave Chinner [this message]
2014-06-10 10:14 ` [PATCH v3] " Filipe David Borba Manana

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=20140610021017.GL4453@dastard \
    --to=david@fromorbit.com \
    --cc=fdmanana@gmail.com \
    --cc=fstests@vger.kernel.org \
    --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 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).