public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: Anand Jain <anand.jain@oracle.com>, Zorro Lang <zlang@redhat.com>,
	Filipe Manana <fdmanana@suse.com>,
	"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/7] fstests: add tests for btrfs' raid-stripe-tree feature
Date: Wed, 6 Dec 2023 07:48:09 +0000	[thread overview]
Message-ID: <6c8af644-8a73-46b4-81fa-932da87b54be@wdc.com> (raw)
In-Reply-To: <CAL3q7H56L7+m6-SX6oqoaDu89u-QNVR-0F=G3bSt+g4S-uSBPg@mail.gmail.com>

On 05.12.23 20:50, Filipe Manana wrote:
> 
> Just one more thing, and sorry I didn't notice before. All the tests fail
> when running with compression enabled, for example:

Well yeah this is kind of obvious why it happens (now that I see it). 
I'll skip the tests in case of enabled compression.

> Also, they all fail when the free space tree is disabled, like this:
> 
> root 19:45:30 /home/fdmanana/git/hub/xfstests > MKFS_OPTIONS="-O
> ^free-space-tree" ./check btrfs/304
> FSTYP         -- btrfs
> PLATFORM      -- Linux/x86_64 debian0 6.7.0-rc3-btrfs-next-143+ #1 SMP
> PREEMPT_DYNAMIC Mon Dec  4 11:01:37 WET 2023
> MKFS_OPTIONS  -- -O ^free-space-tree /dev/sdb
> MOUNT_OPTIONS -- /dev/sdb /home/fdmanana/btrfs-tests/scratch_1
> 
> btrfs/304 1s ... - output mismatch (see
> /home/fdmanana/git/hub/xfstests/results//btrfs/304.out.bad)
>      --- tests/btrfs/304.out 2023-12-05 19:34:01.040411746 +0000
>      +++ /home/fdmanana/git/hub/xfstests/results//btrfs/304.out.bad
> 2023-12-05 19:45:36.242621419 +0000
>      @@ -15,6 +15,156 @@
>        item 0 key (XXXXXX RAID_STRIPE 4096) itemoff XXXXX itemsize 24
>        encoding: RAID0
>        stripe 0 devid 1 physical XXXXXXXXX
>      + item 1 key (XXXXXX RAID_STRIPE 65536) itemoff XXXXX itemsize 24
>      + encoding: RAID0
>      + stripe 0 devid 1 physical XXXXXXXXX
>      + item 2 key (XXXXXX RAID_STRIPE 65536) itemoff XXXXX itemsize 24
>      ...
>      (Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/304.out
> /home/fdmanana/git/hub/xfstests/results//btrfs/304.out.bad'  to see
> the entire diff)
> Ran: btrfs/304
> Failures: btrfs/304
> Failed 1 of 1 tests

OK I'll investigate why this happens.

> 
> And with nodatacow, only one of them fails:
> 
> root 19:46:16 /home/fdmanana/git/hub/xfstests > MOUNT_OPTIONS="-o
> nodatacow" ./check btrfs/304 btrfs/305 btrfs/306 btrfs/307 btrfs/308
> FSTYP         -- btrfs
> PLATFORM      -- Linux/x86_64 debian0 6.7.0-rc3-btrfs-next-143+ #1 SMP
> PREEMPT_DYNAMIC Mon Dec  4 11:01:37 WET 2023
> MKFS_OPTIONS  -- /dev/sdb
> MOUNT_OPTIONS -- -o nodatacow /dev/sdb /home/fdmanana/btrfs-tests/scratch_1
> 
> btrfs/304 1s ...  1s
> btrfs/305 1s ...  1s
> btrfs/306 1s ...  1s
> btrfs/307 1s ...  1s
> btrfs/308 0s ... - output mismatch (see
> /home/fdmanana/git/hub/xfstests/results//btrfs/308.out.bad)
>      --- tests/btrfs/308.out 2023-12-05 19:37:38.379355089 +0000
>      +++ /home/fdmanana/git/hub/xfstests/results//btrfs/308.out.bad
> 2023-12-05 19:46:33.716457540 +0000
>      @@ -28,9 +28,6 @@
>        item 3 key (XXXXXX RAID_STRIPE 32768) itemoff XXXXX itemsize 24
>        encoding: RAID0
>        stripe 0 devid 1 physical XXXXXXXXX
>      - item 4 key (XXXXXX RAID_STRIPE 8192) itemoff XXXXX itemsize 24
>      - encoding: RAID0
>      - stripe 0 devid 1 physical XXXXXXXXX
>       total bytes XXXXXXXX
>      ...
>      (Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/308.out
> /home/fdmanana/git/hub/xfstests/results//btrfs/308.out.bad'  to see
> the entire diff)
> Ran: btrfs/304 btrfs/305 btrfs/306 btrfs/307 btrfs/308
> Failures: btrfs/308
> Failed 1 of 5 tests
> 
> For the compression, we can just add a "_require_no_compress".
> We should also skip them when free space tree is not enabled or
> nodatacow is enabled for 308 (don't recall if we already have helpers
> for that).
> 
> Other than that, everything looks good to me.

I'm actually thinking of making RST and nodatacow mutually exclusive, as 
nodatacow re-introduces a risk for a RAID write hole.


      reply	other threads:[~2023-12-06  7:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 17:47 [PATCH v3 0/7] fstests: add tests for btrfs' raid-stripe-tree feature Johannes Thumshirn
2023-12-05 17:47 ` [PATCH v3 1/7] fstests: doc: add new raid-stripe-tree group Johannes Thumshirn
2023-12-05 17:47 ` [PATCH v3 2/7] common: add filter for btrfs raid-stripe dump Johannes Thumshirn
2023-12-05 17:47 ` [PATCH v3 3/7] btrfs: add fstest for stripe-tree metadata with 4k write Johannes Thumshirn
2023-12-05 17:47 ` [PATCH v3 4/7] btrfs: add fstest for 8k write spanning two stripes on raid-stripe-tree Johannes Thumshirn
2023-12-05 17:47 ` [PATCH v3 5/7] btrfs: add fstest for writing to a file at an offset with RST Johannes Thumshirn
2023-12-05 17:47 ` [PATCH v3 6/7] btrfs: add fstests to write 128k to a RST filesystem Johannes Thumshirn
2023-12-05 17:47 ` [PATCH v3 7/7] btrfs: add fstest for overwriting a file partially with RST Johannes Thumshirn
2023-12-05 19:50 ` [PATCH v3 0/7] fstests: add tests for btrfs' raid-stripe-tree feature Filipe Manana
2023-12-06  7:48   ` Johannes Thumshirn [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=6c8af644-8a73-46b4-81fa-932da87b54be@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=anand.jain@oracle.com \
    --cc=fdmanana@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zlang@redhat.com \
    /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