From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: linux-btrfs@vger.kernel.org, quwenruo@cn.fujitsu.com, dsterba@suse.cz
Subject: [PATCH v4] btrfs-progs: fsck-tests: verify 'btrfs check --repair' fixes corrupted nlink field
Date: Sat, 15 Apr 2017 14:42:48 +0530 [thread overview]
Message-ID: <20170415091248.GA6323@giis.co.in> (raw)
commit 5cdcc57b8d599f03fe692e0285ee9e17f32267fa
Author: Lakshmipathi.G <Lakshmipathi.G@giis.co.in>
Date: Sat Apr 15 14:26:20 2017 +0530
btrfs-progs: fsck-tests: verify 'btrfs check --repair' fixes corrupted nlink field
Signed-off-by: Lakshmipathi.G <Lakshmipathi.G@giis.co.in>
diff --git a/tests/fsck-tests/026-check-inode-link/test.sh b/tests/fsck-tests/026-check-inode-link/test.sh
new file mode 100755
index 0000000..3a7a3c1
--- /dev/null
+++ b/tests/fsck-tests/026-check-inode-link/test.sh
@@ -0,0 +1,38 @@
+#!/bin/bash
+# verify that 'btrfs check --repair' fixes corrupted inode nlink field
+
+source $TOP/tests/common
+
+check_prereq btrfs-corrupt-block
+check_prereq mkfs.btrfs
+
+setup_root_helper
+prepare_test_dev
+
+test_inode_nlink_field()
+{
+ run_check $SUDO_HELPER "$TOP/mkfs.btrfs" -f "$TEST_DEV"
+
+ run_check_mount_test_dev
+ run_check $SUDO_HELPER touch "$TEST_MNT/test_nlink.txt"
+
+ # find inode_number
+ inode_number=`stat -c%i "$TEST_MNT/test_nlink.txt"`
+ run_check_umount_test_dev
+
+ # corrupt nlink field of inode object
+ run_check $SUDO_HELPER "$TOP/btrfs-corrupt-block" -i "$inode_number" \
+ -f nlink "$TEST_DEV"
+
+ check_image "$TEST_DEV"
+
+ # verify link count
+ run_check_mount_test_dev
+ link_count=`stat -c%h "$TEST_MNT/test_nlink.txt"`
+ run_check_umount_test_dev
+ if [ "$link_count" != 1 ];then
+ _fail "btrfs check --repair: Unable to fix nlink corruption."
+ fi
+}
+
+test_inode_nlink_field
reply other threads:[~2017-04-15 9:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170415091248.GA6323@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).