From nobody Thu Feb 24 16:36:32 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 68D6919E12E1 for ; Thu, 24 Feb 2022 16:36:48 +0000 (UTC) (envelope-from rob.fx907@gmail.com) Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K4JTB6CZVz3Jl7; Thu, 24 Feb 2022 16:36:46 +0000 (UTC) (envelope-from rob.fx907@gmail.com) Received: by mail-ej1-x62c.google.com with SMTP id gb39so5614587ejc.1; Thu, 24 Feb 2022 08:36:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8lypYVqLiCgZAMh2hbiOcaYBXrEVDSnB6m5Tf2siWgU=; b=qTkGC/fhntT1MoXEVtWtcuUIk3qUDq6vHMskEmLlV/R8ADGnPyo5mWF1PPKb59h89V Fozm7WzoUA/SnASU8EJLxRUebPyUwV1VZNymyvSinJarx31ON4ogMyHg4nRL25Yc3WyC eQPs4RL0A4RonT3jsZWwCPOJuWpnkdMJle3opkX1at7B8Or79iMy7Z75WYKAmrrIi2uD e/eTnyLsMRbVPJZm3+GkS8uMdhb7Z91HE9mP3bFXHycU9ukqLL6WPfdVFlsTpWxlhgAE Z6H+mHktuZ6Xa9FAQQ5BwoC5W7NFxI3pAAZ4xU8JpcJEg0i4CFqJv6K55XP0pogbMMEE KP3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8lypYVqLiCgZAMh2hbiOcaYBXrEVDSnB6m5Tf2siWgU=; b=BXgnWz2pIcjyJ+a6b9yzA2ysQQwj1/uHnIZpKisKwLYP91I6RcqAhxmjNsrgu7hR/j t8cRTB9fWuuk6BJ0fYPEtNQ6TDPOoQpC/tqoW6puMyM2+EcJqHTC+am+4I9scYZjJkd0 oob9TntLBrHpfP+6OpLfz/VgdojDZ3CxsxwK+crp06oBHKZQd1nmGBbOhNTShVEolDkZ jxr5/e7iNJspmRUC3v/gx+bl/1YbAy1wMUHxiIA8TtZcd7OpAUazp6cqqEjyTSuoQW1Q hXMpce0JvleqrUWiwe3gJMd7zg+DrFSbeDQaCXTYUc0WZ1ZWQ+G4zsdlqv2yHYlwN+P+ t/Ng== X-Gm-Message-State: AOAM531/eUEs3i87JbxlOxY5yTXBxWzYEzqZX7eQi93NONAoUdkbpD6n F3f14z4fLWgZE/PMsg8ZvzLG8HtXLP//JxrJGimPnVpYeRE= X-Google-Smtp-Source: ABdhPJx4W1CxaQJ//zNhhunxcUXqVYrEaxTkoBQvkr7WH58taBJRSRj4UdQgbo9QPWliQGPtkYyM4Tpyw2hdCU5xb2I= X-Received: by 2002:a17:906:2a92:b0:6cd:4349:dc1a with SMTP id l18-20020a1709062a9200b006cd4349dc1amr2926097eje.648.1645720604457; Thu, 24 Feb 2022 08:36:44 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <07c0c9c34b4a4133acab597c96867d27@lerctr.org> <95c7c326-e2f9-6e66-7b97-b9fb2671f4ad@FreeBSD.org> <1b6b2017ba69e6fda1ca237c3016ac61@lerctr.org> <6182c57bf1859482e72af78037c399e4@lerctr.org> <7abcbe88-446f-44b9-c3a7-0997d3430b57@FreeBSD.org> <2bc12c9ee3e6dd71b65079116ff2b845@lerctr.org> <5930f3d2b71c0932f903bb5b88a3c87d@lerctr.org> In-Reply-To: From: Rob Wing Date: Thu, 24 Feb 2022 07:36:32 -0900 Message-ID: Subject: Re: ZFS PANIC: HELP. To: Alexander Motin Cc: Larry Rosenman , Freebsd current Content-Type: multipart/alternative; boundary="000000000000073ec005d8c6308c" X-Rspamd-Queue-Id: 4K4JTB6CZVz3Jl7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b="qTkGC/fh"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of robfx907@gmail.com designates 2a00:1450:4864:20::62c as permitted sender) smtp.mailfrom=robfx907@gmail.com X-Spamd-Result: default: False [-2.80 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; SUBJ_ALL_CAPS(1.20)[16]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62c:from]; MLMMJ_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --000000000000073ec005d8c6308c Content-Type: text/plain; charset="UTF-8" You might try setting `sysctl vfs.zfs.recover=1` and `sysctl vfs.zfs.spa.load_verify_metadata=0`. I had a similar error the other day (couple months ago). The best I did was being able to import the pool read only. I ended up restoring from backup. On Thu, Feb 24, 2022 at 7:30 AM Alexander Motin wrote: > 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 > > --000000000000073ec005d8c6308c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You might try setting `sysctl vfs.zfs.recover=3D1` an= d `sysctl vfs.zfs.spa.load_verify_metadata=3D0`.

I had a similar error the other day (couple months ago). The best I did=20 was being able to import the pool read only. I ended up restoring from=20 backup.

On Thu, Feb 24, 2022 at 7:30 AM Alexander Motin <mav@freebsd.org> wrote:
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 p= ool
>> on the system),
>> seeL
>> https://www.lerctr.org/~ler/14-BOOT-Crash.png<= /a>
>
> 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.=C2=A0 2) You may treat it as metadata=
corruption: import pool read-only and evacuate the data.=C2=A0 If you have =
recent enough snapshots you may be able to easily replicate the pool
with all the settings to some other disk.=C2=A0 ZIL is not replicated, so <= br> corruptions there should not be a problem.=C2=A0 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

--000000000000073ec005d8c6308c--