public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: dm-log-writes test for fstrim with fsstress
Date: Tue, 22 Oct 2019 15:58:04 +0800	[thread overview]
Message-ID: <20191022075806.16616-1-wqu@suse.com> (raw)

Just to make sure the fstrim is not trimming anything vital (like tree
blocks still in use) on btrfs.

The first patch is to enhance log-writes to check each DISCARD
operation.
The feature is not used in test cases, as it's too time consuming.
But should be a pretty handy feature for small logwrites.

The second patch is the test case.
Which triggers fsstress and a loop of fstrim, all recorded by
dm-log-writes.
Then check each FLUSH after the 'prepare' mark.

The test case in theory can go generic, but I'm using various btrfs
specific hack to speed up the test and has a workaround to avoid false
alert.

So far I haven't triggered a bug.

Qu Wenruo (2):
  fstests: log-writes: Add new discard check point
  fstests: btrfs: dm-logwrites test for fstrim and fsstress workload

 src/log-writes/replay-log.c |  10 ++-
 tests/btrfs/197             | 131 ++++++++++++++++++++++++++++++++++++
 tests/btrfs/197.out         |   2 +
 tests/btrfs/group           |   1 +
 4 files changed, 142 insertions(+), 2 deletions(-)
 create mode 100755 tests/btrfs/197
 create mode 100644 tests/btrfs/197.out

-- 
2.23.0


             reply	other threads:[~2019-10-22  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  7:58 Qu Wenruo [this message]
2019-10-22  7:58 ` [PATCH 1/2] fstests: log-writes: Add new discard check point Qu Wenruo
2019-10-22  7:58 ` [PATCH 2/2] fstests: btrfs: dm-logwrites test for fstrim and fsstress workload Qu Wenruo
2019-10-22  9:09   ` Amir Goldstein
2019-10-22  9:16     ` Qu Wenruo

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=20191022075806.16616-1-wqu@suse.com \
    --to=wqu@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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