From nobody Fri Nov 24 16:45:58 2023 X-Original-To: jail@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 4ScLTL4zBdz52T2m for ; Fri, 24 Nov 2023 16:45:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ScLTL3y0jz3ZwF for ; Fri, 24 Nov 2023 16:45:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1700844358; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cbLqp92n/HGFdkDSbBTUKKd8c7C4+SLH5GGcZIQlGRE=; b=hOvmrzkLVz2ZB2mFcQHPMfYxFK22NB1XN/qjfCX/PlHCi1Aq24r4429QDYFJTDO9z1WkTT AtY6a9YHHjU+kBufml6/zziVEday0HuxsVy2W3k5rWqv0cHjlaw5aqQWguHQUTkq0U7Bo5 PegSfMb14lWXmLXpX7Mz2IQ05WpjUtnkeGNJh8L/wADwH3F8cneQcdBaMVjYC8Rp9A7u5m DBReRXx7W/bUvQHVR5yahbZRHen2L0FvoxMfAF3rkdBpEMaQo+iAybBslRV9whPQkY6tUk iWu7yiw3g3tekb4hLEv03QAqfFCmCksLl4uuuNaU2V5bnTthsckkorp6btDgzw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1700844358; a=rsa-sha256; cv=none; b=TtnaSeEdH5RlgMezhD65zb6F5u+8yrYS4jlOrXsROpcypU89mk5Zx/vV8aTPJtflmpigMw FDM7AxLm9FOWTQ/krivxM/AEicVsuIwmsSCXojxn5ObmCk6z41jpQbZbrfs5DPuT3zcbBo NcG6ghPPfHAqEK1Hb+oWC/Du0tWW6zBbLqHV2c5RR0BxnRZqFfcJaVUc6v8sCX1CL6/NUc KAKHkNMqU2p8DPnEIkhRfYV26MLOmkIv6QNs75LGH51EjcciMO5qQZNsxlhz30577Ke66Z 2iy7WkgrGM96x6aYFNE0BxiRujOkw1iiJRAjplr2nJX8VYe+9R6PogcsjsJ6Nw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4ScLTL2yHXzsLh for ; Fri, 24 Nov 2023 16:45:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 3AOGjwKn027893 for ; Fri, 24 Nov 2023 16:45:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3AOGjwe6027892 for jail@FreeBSD.org; Fri, 24 Nov 2023 16:45:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 275306] 14.0-RELEASE: starting jail causes panic Date: Fri, 24 Nov 2023 16:45:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lexi.freebsd@le-fay.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: jail@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussion about FreeBSD jail(8) List-Archive: https://lists.freebsd.org/archives/freebsd-jail List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-jail@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275306 --- Comment #2 from Lexi --- removing "ossl" seems to have fixed the panic. however, it seems like this has caused permanent damage to several ZFS filesystems / volumes: root@hemlock:~ # zpool status -v pool: data state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A scan: scrub repaired 0B in 8 days 05:00:11 with 0 errors on Thu Nov 16 09:41:34 2023 config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 da0 ONLINE 0 0 0 da3 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: data/iscsi/thyme:<0x1> data/iscsi/willow0:<0x1> /usr/local/poudriere/data/.m/ pool: zroot state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A scan: scrub repaired 0B in 00:02:24 with 0 errors on Wed Nov 8 04:43:50 = 2023 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 ada1p3 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: zroot/jail/amber:<0x0> is this expected? is there any way to recover the data? --=20 You are receiving this mail because: You are the assignee for the bug.=