From: "Lakshmipathi.G" <Lakshmipathi.G@giis.co.in>
To: quwenruo@cn.fujitsu.com, dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: [PATCH v3] btrfs-progs: fsck-tests: verify 'btrfs check --repair' fixes corrupted nlink field
Date: Thu, 2 Feb 2017 13:35:02 +0530 [thread overview]
Message-ID: <20170202080502.GA6676@giis.co.in> (raw)
Signed-off-by: Lakshmipathi.G <Lakshmipathi.G@giis.co.in>
---
tests/fsck-tests/026-check-inode-link/test.sh | 30 +++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100755 tests/fsck-tests/026-check-inode-link/test.sh
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..6822ee2
--- /dev/null
+++ b/tests/fsck-tests/026-check-inode-link/test.sh
@@ -0,0 +1,30 @@
+#!/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 512M
+
+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
+}
+
+test_inode_nlink_field
--
2.7.4
next reply other threads:[~2017-02-02 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 8:05 Lakshmipathi.G [this message]
2017-03-30 15:52 ` [PATCH v3] btrfs-progs: fsck-tests: verify 'btrfs check --repair' fixes corrupted nlink field David Sterba
2017-04-15 9:09 ` Lakshmipathi.G
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=20170202080502.GA6676@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).