mirror_zfs/tests/zfs-tests
Rich Ercolani fa7d572a8a Handle and detect #13709's unlock regression (#14161)
In #13709, as in #11294 before it, it turns out that 63a26454 still had
the same failure mode as when it was first landed as d1d47691, and
fails to unlock certain datasets that formerly worked.

Rather than reverting it again, let's add handling to just throw out
the accounting metadata that failed to unlock when that happens, as
well as a test with a pre-broken pool image to ensure that we never get
bitten by this again.

Fixes: #13709

Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Tony Hutter <hutter2@llnl.gov>
2022-12-01 12:39:43 -08:00
..
callbacks ZTS: Add a failsafe callback to run after each test 2020-03-10 11:00:56 -07:00
cmd Corrected oversight in ZERO_RANGE behavior 2022-04-21 16:58:07 -07:00
include Add options to zfs redundant_metadata property 2022-11-01 12:25:58 -07:00
tests Handle and detect #13709's unlock regression (#14161) 2022-12-01 12:39:43 -08:00
Makefile.am OpenZFS 7503 - zfs-test should tail ::zfs_dbgmsg on test failure 2017-04-12 13:36:48 -07:00