new file mode 100755
@@ -0,0 +1,41 @@
+#!/bin/bash
+
+source $TOP/tests/common
+
+check_prereq btrfs-corrupt-block
+check_prereq mkfs.btrfs
+check_prereq btrfs
+
+setup_root_helper
+prepare_test_dev 512M
+
+ROOT_NODE=256
+BTRFS_DIR_ITEM_KEY=84
+
+# test whether fsck can detect a corrupted dir item name
+test_dir_item_name_field()
+{
+ run_check $SUDO_HELPER $TOP/mkfs.btrfs -f $TEST_DEV
+
+ run_check_mount_test_dev
+ run_check $SUDO_HELPER touch $TEST_MNT/testfile.txt
+
+ run_check_umount_test_dev
+
+ # find key offset
+ key_offset=`$SUDO_HELPER $TOP/btrfs-debug-tree -t FS_TREE $TEST_DEV | \
+ grep -B3 'testfile.txt' | grep "$ROOT_NODE DIR_ITEM" | \
+ cut -f1 -d')' | awk '{print $6}'`
+
+ key=$ROOT_NODE","$BTRFS_DIR_ITEM_KEY","$key_offset
+
+ # corrupt dir item name
+ run_check $SUDO_HELPER $TOP/btrfs-corrupt-block -D -f name \
+ -K $key $TEST_DEV
+
+ $SUDO_HELPER $TOP/btrfs check $TEST_DEV >& /dev/null && \
+ _fail "btrfs check failed to detect corruption"
+ run_check $SUDO_HELPER $TOP/btrfs check --repair $TEST_DEV
+}
+
+test_dir_item_name_field
Please ignore previous 026-dir-item-name-corruption script,it breaks fsck-tests.sh. Use this one instead. This test script aims to detects the corruption even though looks like --repair wont fix the issue. Signed-off-by: Lakshmipathi.G <Lakshmipathi.G@giis.co.in> --- .../026-dir-item-name-corruption/test.sh | 41 ++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100755 tests/fsck-tests/026-dir-item-name-corruption/test.sh