RAIDZ_TEST(1)

✨ RAIDZ_TEST(1) ✨

okay bestie so this is a page from the General Commands Manual, and it's all about raidz_test 💖

🌸 NAME 🌸

raidz_test — the raidz implementation verification and benchmarking tool 🧚

🦋 SYNOPSIS 🦋

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

💜 DESCRIPTION 💜

okay so the whole point of this tool is to run every supported raidz implementation and then verify that all the methods actually produce the right results. no cap. 🫶

it also has a parameter sweep option where every single parameter that affects a RAID-Z block gets verified — think ashift size, data offset, data size, all of it, etc. etc. the tool also supports a benchmarking mode and you get that with the -B option ✨

👑 OPTION 👑

• -h — print a help summary. short, sweet, iconic 💅
• -a ashift (default: 9) — the ashift value. that's it, that's the whole vibe.
• -o zio_off_shift (default: 0) — ZIO offset for each raidz block. the offset's actual value is 2^zio_off_shift 🍓
• -d raidz_data_disks (default: 8) — how many raidz data disks to use. any extra disks you throw in get used for parity. periodt.
• -s zio_size_shift (default: 19) — the size of data for a raidz block. the real size is 2^zio_size_shift ⭐
• -r reflow_offset (default: uint max) — sets the raidz expansion offset. the expanded raidz map allocation function will produce different map configurations depending on this value 👀
• -S(weep) — sweep the parameter space while verifying the raidz implementations. this one will exhaust all most of the valid values for the -aods options. heads up: runtime using this option will be LONG. like, go make a snack long 😭
• -t(imeout) — wall time for the sweep test in seconds. and ngl the actual runtime could be longer than what you asked for.
• -B(enchmark) — all implementations get benchmarked using increasing per disk data size. results come out as throughput per disk, measured in MiB/s 🔥
• -e(xpansion) — use the expanded raidz map allocation function.
• -v(erbose) — increase verbosity. say more, bestie 🗣️
• -T(est the test) — debugging option: fail all the tests. this exists to check whether the tests would properly verify bit-exactness. it's giving "chaos but make it scientific" 💀
• -D(ebug) — debugging option: attach gdb(1) when SIGSEGV or SIGABRT are received. so when it crashes, it crashes fancy 🙈

fr fr, -S and -t are not a quick little errand. plan your day around them.

🌈 SEE ALSO 🌈

ztest(1)

and that's the whole page, bestie 🎀 this was brought to you by OpenZFS, dated May 26, 2021 — love that for us, mwah 💖✨👑