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

[mlelstv%serpens.de@localhost (Michael van Elst)]

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

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-xen/56782: panic: /: bad dir ino null entry
Date: Thu, 7 Apr 2022 09:55:18 -0000 (UTC)

 bartosz%maciejewski.org@localhost (Bartosz Maciejewski) writes:
 
 >The following reply was made to PR port-xen/56782; it has been noted by GNATS.
 
 > Then I enteres fsdb again, and same message popped:
 > 
 > slot 74734 ino 0 reclen 512: regular, 
 > `b94c507e-e227-4457-9dc4-8699d0a6fa72-le64.cache-7'
 > slot 74735 ino 0 reclen 512: regular, 
 > `9add8474-143e-4fa3-8067-31a387cd9cad-le64.cache-7'
 > 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
 > NetBSD/amd64 9#
 
 All the 'ino 0 reclen 512' entries are directory blocks
 with all entries deleted (the names are stale data).
 
 fsdb also always marks the filesystem dirty and writes
 out the warning.
 
 
 Can you show the directory file with e.g.:
 
 hexdump -C /var/cache/fontconfig
 
 ?