On Sun, Dec 17, 2023 at 07:07:40PM +0100, Otto Moerbeek wrote: > On Sun, Dec 17, 2023 at 06:55:27PM +0100, Alexander Klimov wrote: > > > Much better! > > > > Program terminated with signal 11, Segmentation fault. > > #0 0x000008e920ed287f in searchdir (ino=7946491, blkno=Unhandled dwarf > > expression opcode 0xa3 > > ) > > at /usr/src/sbin/dump/traverse.c:474 > > 474 if (TSTINO(dp->d_ino, dumpinomap)) { > > (gdb) info locals > > dblk = 0x3633633264006136 <Address 0x3633633264006136 out of bounds> > > ret = 0 > > loc = 29445 > > mode = Variable "mode" is not available. > > (gdb) p *dblk > > Cannot access memory at address 0x3633633264006136 > > (gdb) p dp > > No symbol "dp" in current context. > > (gdb) p ip > > Variable "ip" is not available. > > (gdb) p ino > > $7 = 7946491 > > (gdb) p blkno > > Unhandled dwarf expression opcode 0xa3 > > (gdb) p size > > $8 = 186 > > (gdb) p filesize > > Unhandled dwarf expression opcode 0xa3 > > (gdb) p tapesize > > Variable "tapesize" is not available. > > (gdb) p nodump > > $9 = 0 > > (gdb) p dp > > No symbol "dp" in current context. > > (gdb) p ip > > Variable "ip" is not available. > > (gdb) p loc > > $10 = 29445 > > (gdb) p dblk > > $11 = 0x3633633264006136 <Address 0x3633633264006136 out of bounds> > > (gdb) p mode > > Variable "mode" is not available. > > (gdb) p ret > > $12 = 0 > > (gdb) > > > > But, admittedly, I'm not very familiar with the code. > > So I can only guess. Too large offset? Too less memory? ... > > > > On 17.12.23 17:27, Otto Moerbeek wrote: > > > Rebuild with > > > cd /usr/src/sbin/dump > > > make obj > > > make clean > > > DEBUG=-g make > > > > > > And then run gdb again. > > Install gdb from packages and then run egdb. It understands moden > DWARF expresssions better. > The value of size is also interesting.
I meant the global mapsize. And while there, dumpinomap is interesting as well. Can you also show $ doas dumpfs /dev/rsd0a |head -20 (replacing rsd0a with your device plus the exact dump command line you are using? -Otto > > Also: is your filesystem clean? To be sure, unmount and run fsck on it. > > -Otto >