Re: fsck segfaults on rpi3 running 13-stable

On Feb 11, 2023, at 14:40, bob prohaska <fbsd@www.zefox.net> wrote:

> While running buildworld on a Pi3 running 13-stable  the machine
> panic'd. On restart using the previous kernel fsck failed with a 
> segfault, which repeated when the disk was moved to a -current Pi3. 
> 
> In single user mode on -current the segfault message is
> 
> ....
> 7912408300994173476 BAD I=74682090
> 4313599915630302063 BAD I=74682090
> -4473632163892877928 BAD I=74682090
> 8068741989830080453 BAD I=74682090
> 3857159125896022134 BAD I=74682090
> -4354179704011695453 BAD I=74682090
> 7611175298055105740 BAD I=74682090
> 3985638883347136889 BAD I=74682090
> -2495754894521232470 BAD I=74682090
> 7739654885841380823 BAD I=74682090
> INODE CHECK-HASH FAILED I=74999808  OWNER=1842251117 MODE=15044
> fsck: /dev/da1s2d: Segmentation fault
> 
> I gather this like unlikely to be recoverable, but it would be 
> nice to understand what went wrong if possible.

Did it produce a *.core file?

I expect that getting a backtrace for the failure would
be desired. So use of a debugger and the *.core --if you
are lucky enough that the backtrace produced ends up
being useful to someone.

I do not know if your builds leave symbols around or not.
(I keep symbols around, even for non-debug builds. But
the symbols are only highly useful some of time for
optimized code.)


===
Mark Millard
marklmi at yahoo.com