diff options
| author | Rich Ercolani <[email protected]> | 2022-11-15 17:44:12 -0500 |
|---|---|---|
| committer | GitHub <[email protected]> | 2022-11-15 14:44:12 -0800 |
| commit | 2163cde450d0898b5f7bac16afb4e238485411ff (patch) | |
| tree | af9a24508cf249c1e7a0c9ea211792a7c990990f /etc/init.d/zfs-mount.in | |
| parent | b445b25b273d263f032fadd717e5731185b74bf5 (diff) | |
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 <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Tony Hutter <[email protected]>
Diffstat (limited to 'etc/init.d/zfs-mount.in')
0 files changed, 0 insertions, 0 deletions