From owner-freebsd-bugs@freebsd.org  Tue Nov  7 10:33:08 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93802E54B74
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  7 Nov 2017 10:33:08 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 823787793B
 for <freebsd-bugs@FreeBSD.org>; Tue,  7 Nov 2017 10:33:08 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vA7AX8hv011485
 for <freebsd-bugs@FreeBSD.org>; Tue, 7 Nov 2017 10:33:08 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 223491] fsck_ufs:  Directory XXXX name not found
Date: Tue, 07 Nov 2017 10:33:08 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: wosch@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-223491-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2017 10:33:08 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223491

            Bug ID: 223491
           Summary: fsck_ufs:  Directory XXXX name not found
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: wosch@FreeBSD.org

I rented a virtual machine running FreeBSD in da data center. The machine
crashed for unknown reasons and fsck did not run successfully. I see on the
console the message:

WARNING: / was not properly dismounted
WARNING: /: mount pendig error: blocks 0 files 1
Starting file system checks:
[...]
** Resolving unreferenced inode list
** Processiong journal entries.
Fsck_ufs: Directory XXXXX name not found
Unknown error 1; help!
ERRROR: ABORTING BOOT (sending SIGTERM to parent)!


And the root shell started.=20

I run fsck manually

# fsck -y=20
** /dev/vtbd0p2
USE JOURNAL? Yes

** SU+J Recovering /dev/vtbd0p2
** Reading 33554432 byte journal from inode 4

RECOVER? Yes
** Building recovery table.
** Resovling unreferenced inode list.
** Processiong journal entries.
fsck_ufs: Directory XXXXX name not found

And it failed again.=20

I googled and some user recommend to use `fsck -y -f=E2=80=99

I tried this and it seems to work, with fsck -y I could repair the filesyst=
em,
run fsck again (without -f) and boot the machine.

I see 2 issues here: why does fsck fails, and print a strange error message?

And second: the manual page fsck(8) is misguiding. It says:

   -f      Force checking of file systems, even when they are marked clean
           (for file systems that support this).=E2=80=9D

This sound like you use -f for checking a clean file system. But in my case=
 it
was rotten. I didn't wanted to check it, I needed to repair it.

--=20
You are receiving this mail because:
You are the assignee for the bug.=