On 02/23/2022 8:41 pm, Alexander Motin wrote:
Hi Larry,
The panic you are getting is an assertion, enabled by kernel built
with INVARIANTS option. On 13 you may just not have that debugging
enabled to hit the issue. But that may be only a consequence.
Original problem I guess in possibly corrupted ZFS intent log records
(or false positive), that could happen so due to use of -F recovery
option on `zpool import`, that supposed to try import pool at earlier
transaction group if there is some metadata corruption found. It is
not supposed to work 100% and only a last resort. Though may be that
assertion is just excessively strict for that specific recovery case.
If as you say pool can be imported and scrubbed on 13, then I'd expect
following clean export should allow later import on 14 without -F.
On 23.02.2022 21:21, Larry Rosenman wrote:
've got my main dev box that crashes on 14 with the screen shot at
https://www.lerctr.org/~ler/14-zfs-crash.png.
Booting from a 13-REL USB installer it imports and scrubs.
Ideas?
I can either video conference with shared screen or give access to the
console via my Dominion KVM.
Any help/ideas/etc welcome I really need to get this box back.
How can I import the pool withOUT it mounting the FileSystems so I can
export it cleanly on the 13 system?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
