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 09:20:35 +0200

 Well, so fsck took a while an finished:
 
  Â fsck -f -y /dev/rxbd1a
 ** /dev/rxbd1a
 ** Last Mounted on /mnt
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 1310409 files, 1446670100 used, 619525313 free (180849 frags, 77418058 
 blocks, 0.0% fragmentation)
 
 MARK FILE SYSTEM CLEAN? yes
 
 ***** FILE SYSTEM MARKED CLEAN *****
 
 ***** FILE SYSTEM WAS MODIFIED *****
 
 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#
 
 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#
 
 Then again FSCK, and this time I remounted disk image as boot drive to 
 original machine, and same happened.
 
 Updating fontconfig cache:[Â  29.7600677] panic: /: bad dir ino 30113744 
 at offset 33300480: null entry
 
 [Â  29.7600677] cpu0: Begin traceback...
 [Â  29.7600677] vpanic() at netbsd:vpanic+0x143
 [Â  29.7600677] snprintf() at netbsd:snprintf
 [Â  29.7600677] ufs_lookup() at netbsd:ufs_lookup+0x3ba
 [Â  29.7600677] VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x34
 [Â  29.7700883] lookup_once() at netbsd:lookup_once+0x18b
 [Â  29.7700883] namei_tryemulroot() at netbsd:namei_tryemulroot+0x307
 [Â  29.7700883] namei() at netbsd:namei+0x41
 [Â  29.7700883] fd_nameiat.isra.2() at netbsd:fd_nameiat.isra.2+0x54
 [Â  29.7700883] do_sys_linkat() at netbsd:do_sys_linkat+0xc6
 [Â  29.7700883] sys_link() at netbsd:sys_link+0x25
 [Â  29.7700883] syscall() at netbsd:syscall+0x9c
 [Â  29.7700883] --- syscall (number 9) ---
 [Â  29.7700883] 7a8c09a433ca:
 [Â  29.7700883] cpu0: End traceback...
 
 [Â  29.7700883] dumping to dev 142,1 (offset=2097151, size=0): not possible
 [Â  29.7700883] rebooting...
 
 Also, even after fsdb and fsck, I'm unable to do ls after entering 
 /var/cache/fontconfig, nor # rm -rf /var/cache/fontconfig/
 
 It actually hangs, or will panic soon (leaving it to see outcome of rm)
 
 
 
 W dniu 06.04.2022 o 19:29, Martin Husemann pisze:
 > On Wed, Apr 06, 2022 at 07:26:32PM +0200, Bartosz Maciejewski wrote:
 >> slot 74735 ino 0 reclen 512: regular,
 >> `9add8474-143e-4fa3-8067-31a387cd9cad-le64.cache-7'
 >> DIRECTORY ?: CONTAINS EMPTY BLOCKS
 >> ADJUST LENGTH? [yn] y
 >>
 >> YOU MUST RERUN FSCK AFTERWARDS
 >>
 >> I will reru fsck as advised, and then do fsdb once again. But every time I
 >> just run fsck it is marking this dev as clean, but panic is not fixed.
 > Cool, if that fixes it, we should teach fsck to do the same check and
 > fix it directly (w/o manual fsdb).
 >
 > Martin