From: Brian Foster <bfoster@redhat.com>
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH v2] generic/388: randomly recover via read-only mounts
Date: Tue, 5 Jan 2021 06:58:44 -0500 [thread overview]
Message-ID: <20210105115844.293207-1-bfoster@redhat.com> (raw)
XFS has an issue where superblock counters may not be properly
synced when recovery occurs via a read-only mount. This causes the
filesystem to become inconsistent after unmount. To cover this test
case, update generic/388 to switch between read-only and read-write
mounts to perform log recovery.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
v2:
- Tweak ro -> rw mount cycle error message to be unique.
v1: https://lore.kernel.org/fstests/20201217145941.2513069-1-bfoster@redhat.com/
tests/generic/388 | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/tests/generic/388 b/tests/generic/388
index 451a6be2..2f97f266 100755
--- a/tests/generic/388
+++ b/tests/generic/388
@@ -66,8 +66,14 @@ for i in $(seq 1 $((50 * TIME_FACTOR)) ); do
ps -e | grep fsstress > /dev/null 2>&1
done
- # quit if mount fails so we don't shutdown the host fs
- _scratch_cycle_mount || _fail "cycle mount failed"
+ # Toggle between rw and ro mounts for recovery. Quit if any mount
+ # attempt fails so we don't shutdown the host fs.
+ if [ $((RANDOM % 2)) -eq 0 ]; then
+ _scratch_cycle_mount || _fail "cycle mount failed"
+ else
+ _scratch_cycle_mount "ro" || _fail "cycle ro mount failed"
+ _scratch_cycle_mount || _fail "cycle rw mount failed"
+ fi
done
# success, all done
--
2.26.2
next reply other threads:[~2021-01-05 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 11:58 Brian Foster [this message]
2021-01-05 17:31 ` [PATCH v2] generic/388: randomly recover via read-only mounts Darrick J. Wong
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=20210105115844.293207-1-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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