From: "Flint.Wang" <hmsjwzb@zoho.com>
To: dsterba@suse.cz, nborisov@suse.com, josef@toxicpanda.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] btrfs/219: fix problems with mount old generation
Date: Wed, 27 Jul 2022 17:16:57 +0800 [thread overview]
Message-ID: <20220727091657.4998-1-hmsjwzb@zoho.com> (raw)
In-Reply-To: <1aaff0ac-436e-7782-081c-3549ff3d8c8f@zoho.com>
Hi Nikolay & David,
As we discussed, I changed the test btrfs/219 to make it pass.
This test try to mount btrfs filesystem with old generation.
Devices are matched by UUID in btrfs filesystem. The mount of btrfs with
old generation should be failed on purpose.
Signed-off-by: Flint.Wang <hmsjwzb@zoho.com>
---
tests/btrfs/219 | 3 +--
tests/btrfs/219.out | 1 +
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/btrfs/219 b/tests/btrfs/219
index 528175b8..5152fa91 100755
--- a/tests/btrfs/219
+++ b/tests/btrfs/219
@@ -73,8 +73,7 @@ _mount $loop_dev $loop_mnt > /dev/null 2>&1 || \
$UMOUNT_PROG $loop_mnt
_mount -o loop $fs_img2 $loop_mnt > /dev/null 2>&1 || \
- _fail "We couldn't mount the old generation"
-$UMOUNT_PROG $loop_mnt
+ echo "We couldn't mount the old generation"
_mount $loop_dev $loop_mnt > /dev/null 2>&1 || \
_fail "Failed to mount the second time"
diff --git a/tests/btrfs/219.out b/tests/btrfs/219.out
index 162074d3..6fe85f24 100644
--- a/tests/btrfs/219.out
+++ b/tests/btrfs/219.out
@@ -1,2 +1,3 @@
QA output created by 219
+We couldn't mount the old generation
Silence is golden
--
2.37.0
Thanks
prev parent reply other threads:[~2022-07-27 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 8:36 [PATCH]btrfs: Fix fstest case btrfs/219 Flint.Wang
2022-07-21 13:37 ` Nikolay Borisov
2022-07-22 5:34 ` hmsjwzb
2022-07-22 8:52 ` Nikolay Borisov
2022-07-26 18:38 ` David Sterba
2022-08-03 6:19 ` Anand Jain
2022-07-27 9:16 ` Flint.Wang [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=20220727091657.4998-1-hmsjwzb@zoho.com \
--to=hmsjwzb@zoho.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.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;
as well as URLs for NNTP newsgroup(s).