Re: port-xen/56782: panic: /: bad dir ino null entry

[Bartosz Maciejewski <bartosz%maciejewski.org@localhost>]

The following reply was made to PR port-xen/56782; it has been noted by GNATS.

From: Bartosz Maciejewski <bartosz%maciejewski.org@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: port-xen/56782: panic: /: bad dir ino null entry
Date: Thu, 7 Apr 2022 11:52:07 +0200

 On it. I got it now as disk in original machine from which I booted and 
 ctrl+c fontconfig rebuild. In fstab there is log option (journal), and 
 while fscking it replayed jourlnal, shoud I reboot/mount it on system 
 without journal or it is irrevelant in this case?
 
 fsdb (inum: 30113744)> clri 30113744
 fsdb (inum: 30113744)> exit
 *** FILE SYSTEM MARKED DIRTY
 *** BE SURE TO RUN FSCK TO CLEAN UP ANY DAMAGE
 *** IF IT WAS MOUNTED, RE-MOUNT WITH -u -o reload
 BAD_dom# fsck -f -y /dev/rxbd0a
 ** /dev/rxbd0a
 ** File system is journaled; replaying journal
 ** Last Mounted on /
 ** Root file system
 ** Phase 1 - Check Blocks and Sizes
 
 W dniu 07.04.2022 o 11:45, Martin Husemann pisze:
 > So it looks like that directory has a bunch of blocks that got zeroed.
 > This could be fallout from various things - including a bad block on the
 > disk and the drive firmware remapping it to a spare.
 >
 > The way forward probably is to kill the directory completely, by using
 >
 >    fsdb (inum: 2) > clri 30113744
 >
 > and then run fsck again (which will collect all the files in that dir
 > into /lost+found, but since it is a cache it doesn't matter and you can
 > delete them).
 >
 > I'm not sure if you need to create a new empty /var/cache/fontconfig
 > dir or if it will happen automatically on reboot, but after that everything
 > should be ok again.
 >
 > Martin