Date: Thu, 24 Feb 2022 11:29:02 -0500 From: Alexander Motin <mav@FreeBSD.org> To: Larry Rosenman <ler@lerctr.org> Cc: Freebsd current <freebsd-current@freebsd.org> Subject: Re: ZFS PANIC: HELP. Message-ID: <e9b95fed-9a3c-623c-c046-f0a7fd609eb6@FreeBSD.org> In-Reply-To: <5930f3d2b71c0932f903bb5b88a3c87d@lerctr.org> References: <07c0c9c34b4a4133acab597c96867d27@lerctr.org> <95c7c326-e2f9-6e66-7b97-b9fb2671f4ad@FreeBSD.org> <1b6b2017ba69e6fda1ca237c3016ac61@lerctr.org> <a5f379a6-c2bd-f1e9-a281-bb657f3ccb75@FreeBSD.org> <6182c57bf1859482e72af78037c399e4@lerctr.org> <7abcbe88-446f-44b9-c3a7-0997d3430b57@FreeBSD.org> <2bc12c9ee3e6dd71b65079116ff2b845@lerctr.org> <5930f3d2b71c0932f903bb5b88a3c87d@lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24.02.2022 10:57, Larry Rosenman wrote: > On 02/23/2022 9:27 pm, Larry Rosenman wrote: >> It crashes just after root mount (this is the boot pool and only pool >> on the system), >> seeL >> https://www.lerctr.org/~ler/14-BOOT-Crash.png > > Where do I go from here? I see 2 ways: 1) Since it is only an assertion and 13 is working (so far), you may just build 14 kernel without INVARIANTS option and later recreate the pool when you have time. 2) You may treat it as metadata corruption: import pool read-only and evacuate the data. If you have recent enough snapshots you may be able to easily replicate the pool with all the settings to some other disk. ZIL is not replicated, so corruptions there should not be a problem. If there are no snapshots, then either copy on file level, or you may be able to create snapshot for replication in 13 (on 14 without INVARIANTS), importing pool read-write. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e9b95fed-9a3c-623c-c046-f0a7fd609eb6>