public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guan@eryu.me>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
	Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs: test creating a snapshot after RWF_NOWAIT write works as expected
Date: Mon, 20 Jul 2020 00:44:17 +0800	[thread overview]
Message-ID: <20200719164417.GC2557159@desktop> (raw)
In-Reply-To: <20200615175028.15090-1-fdmanana@kernel.org>

On Mon, Jun 15, 2020 at 06:50:28PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Test that creating a snapshot after writing to a file using a RWF_NOWAIT
> works, does not hang the snapshot creation task, and we are able to read
> the data after.
> 
> Currently btrfs hangs when creating the snapshot due to a missing unlock
> of a snapshot lock, but it is fixed by a patch with the following subject:
> 
>   "btrfs: fix hang on snapshot creation after RWF_NOWAIT write"
> 
> Signed-off-by: Filipe Manana <fdmanana@suse.com>

So sorry for the late review.. But I hit the following failure with
v5.8-rc5 kernel, which contains the mentioned fix

 QA output created by 215
 wrote 65536/65536 bytes at offset 0
 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 65536/65536 bytes at offset 0
-XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+pwrite: Input/output error
 Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap'
 File data in the subvolume:
-0000000 fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
+0000000 ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab
 *
 0065536
 File data in the snapshot:
-0000000 fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
+0000000 ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab
 *
 0065536

And I did hit hang when testing without the fix. Is this something that
should be fixed in the test?

Thanks,
Eryu

> ---
>  tests/btrfs/214     | 66 +++++++++++++++++++++++++++++++++++++++++++++
>  tests/btrfs/214.out | 14 ++++++++++
>  tests/btrfs/group   |  1 +
>  3 files changed, 81 insertions(+)
>  create mode 100755 tests/btrfs/214
>  create mode 100644 tests/btrfs/214.out
> 
> diff --git a/tests/btrfs/214 b/tests/btrfs/214
> new file mode 100755
> index 00000000..c835e844
> --- /dev/null
> +++ b/tests/btrfs/214
> @@ -0,0 +1,66 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (C) 2020 SUSE Linux Products GmbH. All Rights Reserved.
> +#
> +# FSQA Test No. 214
> +#
> +# Test that creating a snapshot after writing to a file using a RWF_NOWAIT
> +# works, does not hang the snapshot creation task, and we are able to read
> +# the data after.
> +#
> +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()
> +{
> +	cd /
> +	rm -f $tmp.*
> +}
> +
> +# get standard environment, filters and checks
> +. ./common/rc
> +. ./common/filter
> +. ./common/attr
> +
> +# real QA test starts here
> +_supported_fs btrfs
> +_supported_os Linux
> +_require_scratch
> +_require_odirect
> +_require_xfs_io_command pwrite -N
> +_require_chattr C
> +
> +rm -f $seqres.full
> +
> +_scratch_mkfs >>$seqres.full 2>&1
> +_scratch_mount
> +
> +# RWF_NOWAIT writes require NOCOW
> +touch $SCRATCH_MNT/f
> +$CHATTR_PROG +C $SCRATCH_MNT/f
> +
> +$XFS_IO_PROG -d -c "pwrite -S 0xab 0 64K" $SCRATCH_MNT/f | _filter_xfs_io
> +
> +# Now do a WEF_WRITE into a range containing a NOCOWable extent.
> +$XFS_IO_PROG -d -c "pwrite -N -V 1 -S 0xfe 0 64K" $SCRATCH_MNT/f \
> +	| _filter_xfs_io
> +
> +$BTRFS_UTIL_PROG subvolume snapshot -r $SCRATCH_MNT $SCRATCH_MNT/snap \
> +	| _filter_scratch
> +
> +# Unmount, mount again and verify the file in the subvolume and snapshot has
> +# the correct data.
> +_scratch_cycle_mount
> +
> +echo "File data in the subvolume:"
> +od -A d -t x1 $SCRATCH_MNT/f
> +
> +echo "File data in the snapshot:"
> +od -A d -t x1 $SCRATCH_MNT/snap/f
> +
> +status=0
> +exit
> diff --git a/tests/btrfs/214.out b/tests/btrfs/214.out
> new file mode 100644
> index 00000000..6cc66972
> --- /dev/null
> +++ b/tests/btrfs/214.out
> @@ -0,0 +1,14 @@
> +QA output created by 214
> +wrote 65536/65536 bytes at offset 0
> +XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +wrote 65536/65536 bytes at offset 0
> +XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +Create a readonly snapshot of 'SCRATCH_MNT' in 'SCRATCH_MNT/snap'
> +File data in the subvolume:
> +0000000 fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
> +*
> +0065536
> +File data in the snapshot:
> +0000000 fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
> +*
> +0065536
> diff --git a/tests/btrfs/group b/tests/btrfs/group
> index 9e48ecc1..a3706e7d 100644
> --- a/tests/btrfs/group
> +++ b/tests/btrfs/group
> @@ -216,3 +216,4 @@
>  211 auto quick log prealloc
>  212 auto balance dangerous
>  213 auto balance dangerous
> +214 auto quick snapshot
> -- 
> 2.26.2

  reply	other threads:[~2020-07-19 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 17:50 [PATCH] btrfs: test creating a snapshot after RWF_NOWAIT write works as expected fdmanana
2020-07-19 16:44 ` Eryu Guan [this message]
2020-07-19 18:23   ` Filipe Manana
2020-07-19 18:45     ` Eryu Guan

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=20200719164417.GC2557159@desktop \
    --to=guan@eryu.me \
    --cc=fdmanana@kernel.org \
    --cc=fdmanana@suse.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