Rich Ercolani 2163cde450 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-11-15 14:44:12 -08:00
..
common.run	Handle and detect #13709's unlock regression (#14161)	2022-11-15 14:44:12 -08:00
freebsd.run	Expose additional file level attributes	2022-03-07 17:52:03 -08:00
linux.run	Support idmapped mount in user namespace	2022-11-08 10:28:56 -08: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	Add zilstat script to report zil kstats in a user friendly manner	2022-09-02 13:24:07 -07:00
sunos.run	ZTS: Add a failsafe callback to run after each test	2020-03-10 11:00:56 -07:00