From: "Lakshmipathi.G" <Lakshmipathi.G@giis.co.in>
To: dsterba@suse.cz, quwenruo@cn.fujitsu.com, linux-btrfs@vger.kernel.org
Subject: [PATCH v4] btrfs-progs: misc-tests: Superblock corruption and recovery using backup
Date: Sat, 15 Apr 2017 15:43:08 +0530 [thread overview]
Message-ID: <20170415101308.GA7614@giis.co.in> (raw)
Signed-off-by: Lakshmipathi.G <Lakshmipathi.G@giis.co.in>
---
.../020-fix-superblock-corruption/test.sh | 35 ++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100755 tests/misc-tests/020-fix-superblock-corruption/test.sh
diff --git a/tests/misc-tests/020-fix-superblock-corruption/test.sh b/tests/misc-tests/020-fix-superblock-corruption/test.sh
new file mode 100755
index 0000000..0faebad
--- /dev/null
+++ b/tests/misc-tests/020-fix-superblock-corruption/test.sh
@@ -0,0 +1,35 @@
+#!/bin/bash
+#
+# Corrupt primary superblock and restore it using backup superblock.
+#
+
+source $TOP/tests/common
+
+check_prereq btrfs-select-super
+check_prereq btrfs
+
+setup_root_helper
+prepare_test_dev
+
+FIRST_SUPERBLOCK_OFFSET=65536
+
+test_superblock_restore()
+{
+ run_check $SUDO_HELPER "$TOP/mkfs.btrfs" -f "$TEST_DEV"
+
+ # Corrupt superblock checksum
+ run_check $SUDO_HELPER dd if=/dev/zero of="$TEST_DEV" \
+ seek="$FIRST_SUPERBLOCK_OFFSET" bs=1 count=4 conv=notrunc
+
+ # Run btrfs check to detect corruption
+ run_mayfail "$TOP/btrfs" check "$TEST_DEV" && \
+ _fail "btrfs check should detect corruption"
+
+ # Copy backup superblock to primary
+ run_check "$TOP/btrfs-select-super" -s 1 "$TEST_DEV"
+
+ #Performing btrfs check
+ run_check "$TOP/btrfs" check "$TEST_DEV"
+}
+
+test_superblock_restore
--
2.7.4
next reply other threads:[~2017-04-15 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 10:13 Lakshmipathi.G [this message]
2017-04-19 17:06 ` [PATCH v4] btrfs-progs: misc-tests: Superblock corruption and recovery using backup David Sterba
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=20170415101308.GA7614@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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).