public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonlist@gmail.com>
To: Omar Sandoval <osandov@osandov.com>, linux-block@vger.kernel.org
Cc: kernel-team@fb.com
Subject: Re: Announcing blktests
Date: Mon, 15 May 2017 15:13:52 +0300	[thread overview]
Message-ID: <87h90m71xb.fsf@dmlp.sw.ru> (raw)
In-Reply-To: <20170512184905.GA15267@vader.DHCP.thefacebook.com>

Omar Sandoval <osandov@osandov.com> writes:

> Hi, everyone,
>
> At LSF/MM, we talked about the need for somewhere to dump tests for the
> block layer/storage stack. I've put together a test suite inspired by
> xfstests here: https://github.com/osandov/blktests.
>
> I started out with the opinion that we should reuse xfstests for this,
> but it became clear that the requirements for testing block devices are
> slightly different, and it diverged significantly from there. In
> particular, blktests supports:
>
> - Per-device tests. You can configure a list of test devices and the
>   per-device tests will run on each one (currently in serial, we can
>   support parallel runs in the future if needed).
> - No-device tests. Some tests don't need to run on real hardware, and we
>   can just set up a null-blk or scsi-debug device.
> - Performance numbers. In addition to the output comparison pass/fail
>   that xfstests supports, blktests can also report arbitrary test
>   metrics which don't affect whether the test passes but can be useful
>   for spotting regressions.
Cool. Thank you.
It would be nice to have hermetic kvm environment similar to
xfstests-bld [1] . I'm a volunteer to do that.

Also I'm interested in adding my t10-dif csum tests.
Is this ok to add it to separate ./tests/t10-dif group ?

Side observations:
Observation #1
I've run this on fresh fedora kernel and it hit panic on the very first tests,
which is very good sign for regression test framework.
Observation #2
It is appeared that git tree was corrupted after crash  :) Defenitely fsync is missed
somewhere in git-core, I've straced it and found 'git clone' does only
two fsync for tmp-pack-xxx files. It seems git's crash consistency is horrably broken.
>
> Jens and I wrote up an initial set of tests, but there are a lot more we
> can still write. I'm also happy to take feature requests, just email me
> or open an issue on the GitHub repo.
>
> Thanks,
> Omar

Footnotes: 
[1]  https://github.com/tytso/xfstests-bld

  parent reply	other threads:[~2017-05-15 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 18:49 Announcing blktests Omar Sandoval
2017-05-15  7:44 ` Johannes Thumshirn
2017-05-15 17:30   ` Omar Sandoval
2017-05-15 12:13 ` Dmitry Monakhov [this message]
2017-05-15 15:30   ` Christoph Hellwig
2017-05-15 17:35   ` Omar Sandoval

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=87h90m71xb.fsf@dmlp.sw.ru \
    --to=dmonlist@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@osandov.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