Google Git
Sign in
chromium / external / github.com / osandov / blktests / 433656101a1c09489652cf11ac7aabddfe0aaa32
commit433656101a1c09489652cf11ac7aabddfe0aaa32[log] [tgz]
authorAndré Almeida <andrealmeid@collabora.com>Tue Oct 22 14:17:23 2019
committerOmar Sandoval <osandov@osandov.com>Wed Nov 13 20:27:59 2019
tree3ff11534ea681884ca906721959340736cce5bab
parent4a5d2e87d654255dd5cda791bbc716a847046ec6 [diff]
block/013: Finish removing obsolete license header

Commit e9ffecc "Convert license headers to SPDX tags" remove extensive
license description and replace with a SPDX tag. However, one line was
left behind. Remove this line.

Signed-off-by: André Almeida <andrealmeid@collabora.com>
1 file changed
tree: 3ff11534ea681884ca906721959340736cce5bab
  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, Arch Linux) 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 (note: these tests are potentially destructive):

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

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

Do not 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.