Clone this repo:
  1. 06f0fd7 zbd/006: Test revalidate during other I/O requests by Shin'ichiro Kawasaki · 2 days ago master
  2. 7e32724 add checking nvmet module in nvme 002,003,004,015,018 test by Xiao Liang · 2 days ago
  3. baccddc Fix checking multiple modules error in _have_modules() by Xiao Liang · 11 days ago
  4. de5ef08 nvme: test out-of-range I/O access (file backend) by Sagi Grimberg · 12 days ago
  5. 2347174 nvme: add udevadm settle before disconnecting by Sagi Grimberg · 12 days ago

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.