From nobody Sun Jun 20 12:40:18 2021 X-Original-To: fs@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 A96785D0E24 for ; Sun, 20 Jun 2021 12:40:18 +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 4G7C1G3nZ1z3Dpc for ; Sun, 20 Jun 2021 12:40:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 5A93F1A44 for ; Sun, 20 Jun 2021 12:40:18 +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 15KCeI0E023914 for ; Sun, 20 Jun 2021 12:40:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 15KCeI6t023913 for fs@FreeBSD.org; Sun, 20 Jun 2021 12:40:18 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: fs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyNTY3MTJdIFVGUzoga2VybmVsIHBhbmljOiBmZnNfYmxr?= =?UTF-8?B?ZnJlZV9jZzogZnJlZWluZyBmcmVlIGZyYWcg4oCTIGluIHJlc3BvbnNlIHRv?= =?UTF-8?B?IHBrZy1kZWxldGUoOCkgc29vbiBhZnRlciBsb2dpbg==?= Date: Sun, 20 Jun 2021 12:40:18 +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: 13.0-RELEASE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: andrew@tao11.riddles.org.uk X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@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: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256712 --- Comment #7 from andrew@tao11.riddles.org.uk --- I've been trying to help Graham reproduce this one (per discussions on the libera #freebsd irc channel) but so far what I seem to have managed is to produce a different error: ** SU+J Recovering /dev/vtbd1 ** Reading 4194304 byte journal from inode 4. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. /dev/vtbd1: ino_remref: ino 2767 mode 0100000 about to go negative /dev/vtbd1: UNEXPECTED SU+J INCONSISTENCY /dev/vtbd1: INTERNAL ERROR: GOT TO reply() /dev/vtbd1: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. I've managed to reproduce this one fairly reliably (3 times out of 4 tries)= and I have a copy of a filesystem image taken before the fsck. The steps I used= to reproduce were (this is in a 13-stable install in a bhyve vm, where vtbd0 is the system image and vtbd1 is a 256MB md device on the host): newfs -O2 -U -j /dev/vtbd1 mount /dev/vtbd1 /mnt tar -xf python38-3.8.10.tgz -C /mnt find /mnt/usr -type f -print0 | xargs -0 rm tar -xf python38-3.8.10.tgz -C /mnt (when the prompt returns at this point, immediately destroy the vm) On booting the vm again and then doing fsck -p /dev/vtbd1, the above error appears. (vtbd1 is not mentioned in fstab) Should I split this off into a separate bug? (I will continue to try to reproduce the original issue) --=20 You are receiving this mail because: You are the assignee for the bug.=