public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Ma Xinjian <xinjianx.ma@intel.com>
To: fstests@vger.kernel.org
Cc: Philip Li <philip.li@intel.com>,
	kernel test robot <lkp@intel.com>,
	Ma Xinjian <xinjianx.ma@intel.com>
Subject: [PATCH 1/2] btrfs/049: remove the test
Date: Mon, 27 Sep 2021 15:20:18 +0800	[thread overview]
Message-ID: <20210927072019.46609-1-xinjianx.ma@intel.com> (raw)

inode_cache is deprecated and will never appear in mount
options; remove it entirely

Link: https://www.spinics.net/lists/linux-btrfs/msg107910.html
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Ma Xinjian <xinjianx.ma@intel.com>
---
 tests/btrfs/049 | 85 -------------------------------------------------
 1 file changed, 85 deletions(-)
 delete mode 100755 tests/btrfs/049

diff --git a/tests/btrfs/049 b/tests/btrfs/049
deleted file mode 100755
index 87c205ca..00000000
--- a/tests/btrfs/049
+++ /dev/null
@@ -1,85 +0,0 @@
-#! /bin/bash
-# SPDX-License-Identifier: GPL-2.0
-# Copyright (c) 2014 Fujitsu.  All Rights Reserved.
-#
-# FS QA Test No. btrfs/049
-#
-# Regression test for btrfs inode caching vs tree log which was
-# addressed by the following kernel patch.
-#
-# Btrfs: fix inode caching vs tree log
-#
-. ./common/preamble
-_begin_fstest auto quick
-
-# Override the default cleanup function.
-_cleanup()
-{
-	_cleanup_flakey
-	rm -rf $tmp
-}
-
-# Import common functions.
-. ./common/filter
-. ./common/dmflakey
-
-# real QA test starts here
-_supported_fs btrfs
-_require_scratch
-_require_dm_target flakey
-# Zoned btrfs does not support inode cache
-_require_non_zoned_device "$SCRATCH_DEV"
-
-_scratch_mkfs >> $seqres.full 2>&1
-
-SAVE_MOUNT_OPTIONS="$MOUNT_OPTIONS"
-MOUNT_OPTIONS="$MOUNT_OPTIONS -o inode_cache,commit=100"
-
-# create a basic flakey device that will never error out
-_init_flakey
-_mount_flakey
-
-_get_inode_id()
-{
-	local inode_id
-	inode_id=`stat $1 | grep Inode: | $AWK_PROG '{print $4}'`
-	echo $inode_id
-}
-
-$XFS_IO_PROG -f -c "pwrite 0 10M" -c "fsync" \
-	$SCRATCH_MNT/data >& /dev/null
-
-inode_id=`_get_inode_id "$SCRATCH_MNT/data"`
-rm -f $SCRATCH_MNT/data
-
-for i in `seq 1 5`;
-do
-	mkdir $SCRATCH_MNT/dir_$i
-	new_inode_id=`_get_inode_id $SCRATCH_MNT/dir_$i`
-	if [ $new_inode_id -eq $inode_id ]
-	then
-		$XFS_IO_PROG -f -c "pwrite 0 1M" -c "fsync" \
-			$SCRATCH_MNT/dir_$i/data1 >& /dev/null
-		_load_flakey_table 1
-		_unmount_flakey
-		need_umount=1
-		break
-	fi
-	sleep 1
-done
-
-# restore previous mount options
-export MOUNT_OPTIONS="$SAVE_MOUNT_OPTIONS"
-
-# ok mount so that any recovery that needs to happen is done
-if [ $new_inode_id -eq $inode_id ];then
-	_load_flakey_table $FLAKEY_ALLOW_WRITES
-	_mount_flakey
-	_unmount_flakey
-fi
-
-# make sure we got a valid fs after replay
-_check_scratch_fs $FLAKEY_DEV
-
-status=0
-exit
-- 
2.20.1


             reply	other threads:[~2021-09-27  7:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27  7:20 Ma Xinjian [this message]
2021-09-27  7:20 ` [PATCH 2/2] btrfs/091: remove noinode_cache option Ma Xinjian
2021-10-24 13:34   ` Eryu Guan
2021-10-25 13:05     ` David Sterba
2021-10-10 13:32 ` [PATCH 1/2] btrfs/049: remove the test Eryu Guan
2021-10-11 10:21   ` 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=20210927072019.46609-1-xinjianx.ma@intel.com \
    --to=xinjianx.ma@intel.com \
    --cc=fstests@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=philip.li@intel.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