linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH] btrfs-progs: misc-tests/034-metadata-uuid remove kernel support
Date: Thu, 21 Sep 2023 06:35:10 +0800	[thread overview]
Message-ID: <c4d569b4e92cbc6ca2a7bd87e0bc0df1758bbba8.1694525360.git.anand.jain@oracle.com> (raw)

The kernel patch, ("btrfs: reject device with CHANGING_FSID_V2 flag"),
removes kernel support for the CHANGING_FSID_V2 flag. So, drop its
related testcase.

Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
Apply this on top of

 [PATCH 0/4 v4] btrfs-progs: recover from failed metadata_uuid port kernel
    btrfs-progs: tune use the latest bdev in fs_devices for super_copy
    btrfs-progs: add support to fix superblock with CHANGING_FSID_V2 flag
    btrfs-progs: recover from the failed btrfstune -m|M
    btrfs-progs: test btrfstune -m|M ability to fix previous failures

 tests/misc-tests/034-metadata-uuid/test.sh | 34 ----------------------
 1 file changed, 34 deletions(-)

diff --git a/tests/misc-tests/034-metadata-uuid/test.sh b/tests/misc-tests/034-metadata-uuid/test.sh
index 0b06f1266f57..852770488051 100755
--- a/tests/misc-tests/034-metadata-uuid/test.sh
+++ b/tests/misc-tests/034-metadata-uuid/test.sh
@@ -222,42 +222,8 @@ failure_recovery_progs() {
 	rm -f -- "$image1" "$image2"
 }
 
-failure_recovery_kernel() {
-	local image1
-	local image2
-	local loop1
-	local loop2
-	local devcount
-
-	reload_btrfs
-
-	image1=$(extract_image "$1")
-	image2=$(extract_image "$2")
-	loop1=$(run_check_stdout $SUDO_HELPER losetup --find --show "$image1")
-	loop2=$(run_check_stdout $SUDO_HELPER losetup --find --show "$image2")
-
-	run_check $SUDO_HELPER udevadm settle
-
-	# Scan to make sure btrfs detects both devices before trying to mount
-	run_check $SUDO_HELPER "$TOP/btrfs" device scan "$loop1"
-	run_check $SUDO_HELPER "$TOP/btrfs" device scan "$loop2"
-
-	# Mount and unmount, on trans commit all disks should be consistent
-	run_check $SUDO_HELPER mount "$loop1" "$TEST_MNT"
-	run_check $SUDO_HELPER umount "$TEST_MNT"
-
-	# perform any specific check
-	"$3" "$loop1" "$loop2"
-
-	# cleanup
-	run_check $SUDO_HELPER losetup -d "$loop1"
-	run_check $SUDO_HELPER losetup -d "$loop2"
-	rm -f -- "$image1" "$image2"
-}
-
 failure_recovery() {
 	failure_recovery_progs $@
-	failure_recovery_kernel $@
 }
 
 reload_btrfs() {
-- 
2.39.3


             reply	other threads:[~2023-09-20 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 22:35 Anand Jain [this message]
2023-10-02 17:10 ` [PATCH] btrfs-progs: misc-tests/034-metadata-uuid remove kernel support David Sterba
2023-10-03  7:49   ` Anand Jain

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=c4d569b4e92cbc6ca2a7bd87e0bc0df1758bbba8.1694525360.git.anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --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).