zfs/tests/runfiles
Rob Norris f5ead99f34 zpool create: warn on suboptimal pool layout
Its possible to create pools that are perfectly valid but are perhaps
not the "best" choice for a given set of devices.

An example is a raidz1 of two devices. I have seen inexperienced users
create this because it looks on the surface like a traditional RAID-1,
that is, a mirror. It even appears to work, but presents problems later
when they want to upgrade the drives, and of course does not perform as
well as a mirror.

This changes `zpool create` to reject such "suboptimal" pool layouts,
and suggest a possible better alternative. It checks for raidz and draid
where the number of devices are parity+1, and could be extended in the
future.

It adds a switch, --force=layout, to disable the check and the warning
and return the old behaviour, for those who know what they're doing.

Included is a utility function to work with option flags. The existing
-f switch to `zpool create` is now an alias for `--force=vdevs`.

Signed-off-by: Rob Norris <robn@despairlabs.com>
2023-07-15 22:56:06 +10:00
..
common.run zpool create: warn on suboptimal pool layout 2023-07-15 22:56:06 +10:00
freebsd.run PAM: enable testing on FreeBSD 2023-05-31 17:01:16 -07:00
linux.run PAM: support password changes even when not mounted 2023-05-31 17:01:11 -07:00
longevity.run OpenZFS 9166 - zfs storage pool checkpoint 2018-06-26 10:07:42 -07:00
perf-regression.run OpenZFS 9184 - Add ZFS performance test for fixed blocksize random read/write IO 2018-07-02 13:46:06 -07:00
sanity.run zpool create: warn on suboptimal pool layout 2023-07-15 22:56:06 +10:00
sunos.run ZTS: Add a failsafe callback to run after each test 2020-03-10 11:00:56 -07:00