Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 07 Nov 2017 10:33:08 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 223491] fsck_ufs:  Directory XXXX name not found
Message-ID:  <bug-223491-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-223491-8>