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

[Robert Elz <kre%munnari.OZ.AU@localhost>]

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

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: Bartosz Maciejewski <bartosz%maciejewski.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost, port-xen-maintainer%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: port-xen/56782: panic: /: bad dir ino null entry
Date: Fri, 08 Apr 2022 01:18:04 +0700

     Date:        Thu, 7 Apr 2022 18:49:59 +0200
     From:        Bartosz Maciejewski <bartosz=40maciejewski.org>
     Message-ID:  <56786d2f-90f0-6388-21ae-3410cc735973=40maciejewski.org>=
 
 
   =7C Guest is running Nagios. Will try to rebuild, or delete and install=
  it=20
   =7C again. Maybe something went off during updates of NetBSD and Nagios=
 .
 
 Unlikely, there's nothing Nagios can do to overwrite directory blocks,
 no matter how hard it tried.
 
 But it is easy for a drive misconfiguration to cause almost
 anything.
 
 Show us (on the guest with the problems) the labels of all drives (or
 pseudo-drives) - all the xbd devices that exist on the system - if they
 are GPT partitioned, show that, otherwise the disklabel.
 
 Also show the contents of /etc/fstab
 
 If you have access to the Dom0 also show the configuration of the guest,
 and any other guests that are running (the drive configuration section is=
 
 what matters) and the labels from any (real) drives connected to that
 system.
 
 Somewhere in all of that is likely to be the cause of the problem.
 Until it is fixed, you want to be very careful using that guest
 system - almost anything might be corrupted next.
 
 kre