public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Anand Jain <anand.jain@oracle.com>, Zorro Lang <zlang@redhat.com>
Cc: Filipe Manana <fdmanana@suse.com>,
	fstests@vger.kernel.org,  linux-btrfs@vger.kernel.org,
	 Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v5 4/9] common: add _require_btrfs_free_space_tree
Date: Thu, 07 Dec 2023 01:03:31 -0800	[thread overview]
Message-ID: <20231207-btrfs-raid-v5-4-44aa1affe856@wdc.com> (raw)
In-Reply-To: <20231207-btrfs-raid-v5-0-44aa1affe856@wdc.com>

Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
---
 common/btrfs | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/common/btrfs b/common/btrfs
index bf69bcee158b..95e46726a801 100644
--- a/common/btrfs
+++ b/common/btrfs
@@ -137,6 +137,16 @@ _require_btrfs_no_block_group_tree()
 	fi
 }
 
+_require_btrfs_free_space_tree()
+{
+	_scratch_mkfs > /dev/null 2>&1
+	if ! $BTRFS_UTIL_PROG inspect-internal dump-super $SCRATCH_DEV | \
+		grep -q "FREE_SPACE_TREE"
+	then
+		_notrun "This test requires a free-space-tree"
+	fi
+}
+
 _check_btrfs_filesystem()
 {
 	device=$1

-- 
2.43.0


  parent reply	other threads:[~2023-12-07  9:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07  9:03 [PATCH v5 0/9] fstests: add tests for btrfs' raid-stripe-tree feature Johannes Thumshirn
2023-12-07  9:03 ` [PATCH v5 1/9] fstests: doc: add new raid-stripe-tree group Johannes Thumshirn
2023-12-07  9:03 ` [PATCH v5 2/9] common: add filter for btrfs raid-stripe dump Johannes Thumshirn
2023-12-07  9:03 ` [PATCH v5 3/9] common: add _require_btrfs_no_nodatacow helper Johannes Thumshirn
2023-12-07  9:03 ` Johannes Thumshirn [this message]
2023-12-07  9:03 ` [PATCH v5 5/9] btrfs: add fstest for stripe-tree metadata with 4k write Johannes Thumshirn
2023-12-07  9:03 ` [PATCH v5 6/9] btrfs: add fstest for 8k write spanning two stripes on raid-stripe-tree Johannes Thumshirn
2023-12-07  9:03 ` [PATCH v5 7/9] btrfs: add fstest for writing to a file at an offset with RST Johannes Thumshirn
2023-12-07  9:03 ` [PATCH v5 8/9] btrfs: add fstests to write 128k to a RST filesystem Johannes Thumshirn
2023-12-07  9:03 ` [PATCH v5 9/9] btrfs: add fstest for overwriting a file partially with RST Johannes Thumshirn
2023-12-07 12:11 ` [PATCH v5 0/9] fstests: add tests for btrfs' raid-stripe-tree feature Filipe Manana
2023-12-08  1:19   ` Anand Jain
2023-12-08  9:19     ` Johannes Thumshirn
2023-12-09 19:15       ` Neal Gompa
2023-12-11  8:49         ` Johannes Thumshirn

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=20231207-btrfs-raid-v5-4-44aa1affe856@wdc.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=anand.jain@oracle.com \
    --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