Re: ZFS PANIC: HELP.
- Reply: Larry Rosenman : "Re: ZFS PANIC: HELP."
- In reply to: Larry Rosenman : "Re: ZFS PANIC: HELP."
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 24 Feb 2022 02:58:22 UTC
On 23.02.2022 21:52, Larry Rosenman wrote: > 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? Why do you need to import without mounting file systems? I think you may actually wish them to be mounted to replay their ZILs. Just use -R option to mount file systems in some different place. -- Alexander Motin