On recent sid I am seeing a segfault with the hfsutils :
$ uname -a
Linux enceladus 5.6.0-1-powerpc64 #1 SMP Debian 5.6.7-1 (2020-04-29)
ppc64 GNU/Linux
dmesg claims :
[ 1268.455231] hfs: filesystem was not cleanly unmounted, running
fsck.hfs is recommended. mounting read-only.
[ 1438.164389] hfs: filesystem was not cleanly unmounted, running
fsck.hfs is recommended. leaving read-only.
enceladus# df -h | grep 'grub'
/dev/sdb2 123M 7.1M 115M 6% /boot/grub
enceladus#
enceladus# umount /dev/sdb2
enceladus# fsck.hfs /dev/sdb2
** /dev/sdb2
** Checking HFS volume.
Segmentation fault
enceladus#
enceladus# TERM=dumb gdb -q /sbin/fsck.hfs
Reading symbols from /sbin/fsck.hfs...
(No debugging symbols found in /sbin/fsck.hfs)
(gdb) run /dev/sdb2
Starting program: /usr/sbin/fsck.hfs /dev/sdb2
** /dev/sdb2
** Checking HFS volume.
Program received signal SIGSEGV, Segmentation fault.
0x000000001001e740 in ?? ()
(gdb) where
#0 0x000000001001e740 in ?? ()
#1 0x0000000010022bd4 in ?? ()
#2 0x0000000010022bd4 in ?? ()
#3 0x0000000010024e60 in ?? ()
#4 0x00000000100203f0 in ?? ()
#5 0x00000000100285c8 in ?? ()
#6 0x0000000010009624 in ?? ()
#7 0x0000000010004f68 in ?? ()
#8 0x0000000010005830 in ?? ()
#9 0x0000000010002014 in ?? ()
#10 0x00007ffff7d5ccb0 in generic_start_main (main=0x10051960,
argc=<optimized out>, argv=0x7ffff5d2a400, auxvec=0x0,
init=<optimized out>, rtld_fini=<optimized out>,
stack_end=<optimized out>, fini=<optimized out>) at ../csu/libc-start.c:308
#11 0x00007ffff7d5cec4 in __libc_start_main (argc=<optimized out>,
argv=<optimized out>, ev=<optimized out>,
auxvec=<optimized out>, rtld_fini=<optimized out>,
stinfo=<optimized out>, stack_on_entry=<optimized out>)
at ../sysdeps/unix/sysv/linux/powerpc/libc-start.c:116
#12 0x0000000000000000 in ?? ()
(gdb) quit
A debugging session is active.
Inferior 1 [process 1879] will be killed.
Quit anyway? (y or n) y
enceladus#
This was a bit of a surprise. I went looking for the sources to hfsutils
and see that it has been slightly revised since 1998 but is largely the
same as it has been for a long long while. Not sure what the SIGSEGV is
being caused by and I think I will wipe the machine and install with the
netinst from 2020-05-30 and hope that a re-partition of the disk and new
hfs boot file filesystem may be clean. Has anyone else seen issues with
the bootable hfs partition?
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
