RAIDZ\_TEST(1) General Commands Manual RAIDZ\_TEST(1)

# [NAME](#NAME)

`raidz_test` — raidz implementation verification and benchmarking tool

# [SYNOPSIS](#SYNOPSIS)

`raidz_test` \[`-StBevTD`] \[`-a` `ashift`] \[`-o` `zio_off_shift`] \[`-d` `raidz_data_disks`] \[`-s` `zio_size_shift`] \[`-r` `reflow_offset`]

# [DESCRIPTION](#DESCRIPTION)

The purpose of this tool is to run all supported raidz implementation and verify the results of all methods. It also contains a parameter sweep option where all parameters affecting a RAID-Z block are verified (like ashift size, data offset, data size, etc.). The tool also supports a benchmarking mode using the `-B` option.

# [OPTION](#OPTION)

[`-h`](#h)

Print a help summary.

[`-a`](#a) `ashift` (default: [**9**](#9))

Ashift value.

[`-o`](#o) `zio_off_shift` (default: [**0**](#0))

ZIO offset for each raidz block. The offset's value is [*2^zio\_off\_shift*](#2_zio_off_shift).

[`-d`](#d) `raidz_data_disks` (default: [**8**](#8))

Number of raidz data disks to use. Additional disks will be used for parity.

[`-s`](#s) `zio_size_shift` (default: [**19**](#19))

Size of data for raidz block. The real size is [*2^zio\_size\_shift*](#2_zio_size_shift).

[`-r`](#r) `reflow_offset` (default: [**uint max**](#uint))

Set raidz expansion offset. The expanded raidz map allocation function will produce different map configurations depending on this value.

[`-S`](#S)(weep)

Sweep parameter space while verifying the raidz implementations. This option will exhaust all most of valid values for the `-aods` options. Runtime using this option will be long.

[`-t`](#t)(imeout)

Wall time for sweep test in seconds. The actual runtime could be longer.

[`-B`](#B)(enchmark)

All implementations are benchmarked using increasing per disk data size. Results are given as throughput per disk, measured in MiB/s.

[`-e`](#e)(xpansion)

Use expanded raidz map allocation function.

[`-v`](#v)(erbose)

Increase verbosity.

[`-T`](#T)(est the test)

Debugging option: fail all tests. This is to check if tests would properly verify bit-exactness.

[`-D`](#D)(ebug)

Debugging option: attach [gdb(1)](/man/os/zfs/gdb.1) when [**SIGSEGV**](#SIGSEGV) or [**SIGABRT**](#SIGABRT) are received.

# [SEE ALSO](#SEE_ALSO)

[ztest(1)](/man/os/zfs/ztest.1)

May 26, 2021 OpenZFS

---

Document: raidz_test(1) from zfs 2.4.4-r4 (Chainguard OS)
Source: https://github.com/openzfs/zfs