NetBSD Problem Report #56942

From dholland@netbsd.org  Wed Jul 27 01:03:23 2022
Return-Path: <dholland@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id DD3AF1A921F
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 27 Jul 2022 01:03:22 +0000 (UTC)
Message-Id: <20220727010322.7AF4D84E9D@mail.netbsd.org>
Date: Wed, 27 Jul 2022 01:03:22 +0000 (UTC)
From: dholland@NetBSD.org
Reply-To: dholland@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: fsck_ffs can't replay wapbl journals to memory
X-Send-Pr-Version: 3.95

>Number:         56942
>Category:       bin
>Synopsis:       fsck_ffs can't replay wapbl journals to memory
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 27 01:05:00 +0000 2022
>Originator:     David A. Holland
>Release:        NetBSD 9.99.99 (20220726)
>Organization:
>Environment:
n/a
>Description:

I discovered recently that although fsck_ffs -n claims it's replaying
the journal, it actually doesn't, because fsck doesn't have the
infrastructure necessary to support replaying the journal without
writing to disk.

I fixed the prints so it no longer claims this; however, since running
fsck without having replayed the journal isn't especially meaningful
or helpful, it would be better to add this functionality.

>How-To-Repeat:

crash, fsck -n, observe inconsistencies, mount and unmount (which
replays the journal), fsck -n again, inconsistencies have disappeared.

>Fix:

SMOP but not entirely trivial :-|

Home	PR Database Search