Google Git
Sign in
chromium / external / github.com / osandov / blktests / 0ee7ebae6324a173fc3ac0d994e810bf4817ee70
commit0ee7ebae6324a173fc3ac0d994e810bf4817ee70[log] [tgz]
authorMing Lei <ming.lei@redhat.com>Mon Apr 15 01:22:29 2019
committerOmar Sandoval <osandov@fb.com>Wed Apr 17 21:41:39 2019
tree19e9fc19adbbad8baa07b44f6ce07314bbcc63c0
parent0a65ba5bd97eef67f792f96a027b31381a3498da [diff]
nvme/012 & 013: avoid extremely slow xfs IO

It is observed that nvme/012 may take ~17 minutes to complete on aarch64,
even worse it may trigger IO timeout on nvme-loop.

Eric and Dave replied that it is because of too small log size on small
disk.

So pass '-l size=32m' to avoid the issue.

With this patch, nvme/012 can be completed in one minute.

Cc: Eric Sandeen <esandeen@redhat.com>
Cc: Dave Chinner <dchinner@redhat.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Signed-off-by: Ming Lei <ming.lei@redhat.com>
2 files changed
tree: 19e9fc19adbbad8baa07b44f6ce07314bbcc63c0
  1. common/
  2. Documentation/
  3. LICENSES/
  4. src/
  5. tests/
  6. .dir-locals.el
  7. .gitignore
  8. .travis.yml
  9. check
  10. CONTRIBUTING.md
  11. Makefile
  12. new
  13. README.md
README.md

blktests

Build Status

blktests is a test framework for the Linux kernel block layer and storage stack. It is inspired by the xfstests filesystem testing framework.

Getting Started

The dependencies are minimal, but make sure you have them installed:

  • bash (>= 4.2)
  • GNU coreutils
  • GNU awk
  • util-linux
  • fio
  • gcc
  • make

Some tests require the following:

  • e2fsprogs and xfsprogs
  • multipath-tools (Debian, openSUSE) or device-mapper-multipath (Fedora)
  • dmsetup (Debian) or device-mapper (Fedora, openSUSE, Arch Linux)

Build blktests with make. Optionally, install it to a known location with make install (/usr/local/blktests by default, but this can be changed by passing DESTDIR and/or prefix).

Add the list of block devices you want to test on in a file named config:

TEST_DEVS=(/dev/nvme0n1 /dev/sdb)

And as root, run the default set of tests with ./check.

Note that these tests are destructive, so don't add anything to the TEST_DEVS array containing data that you want to keep.

See here for more detailed information on configuration and running tests.

Adding Tests

The ./new script creates a new test from a template. The generated template contains more detailed documentation.

Pull requests on GitHub and patches to linux-block@vger.kernel.org are both accepted. See here for more information on contributing.