I am no skilled software developer so this has little meaning to me.. only that I expected a bit more output of this backtrace..
root@ws1000:~# gdb xfs_repair core
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /sbin/xfs_repair...done.
[New LWP 5187]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `xfs_repair -vv -L -P -m 1750 /dev/mapper/vg0-lv0'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007fa8a1e05bcc in _wordcopy_bwd_dest_aligned (dstp=140734808924136,
srcp=98541856, len=2305843009212646584) at wordcopy.c:395
395 wordcopy.c: No such file or directory.
(gdb) bt
#0 0x00007fa8a1e05bcc in _wordcopy_bwd_dest_aligned (dstp=140734808924136,
srcp=98541856, len=2305843009212646584) at wordcopy.c:395
#1 0x0000000000000000 in ?? ()
(gdb) q
root@ws1000:~# uname -r
3.2.0-4-amd64
root@ws1000:~# tail xfs_repair_gdb/xfs_repair-vv-L-P-m1750.out
correcting nextents for inode 28722522
bad data fork in inode 28722522
cleared inode 28722522
inode 28722524 - bad extent starting block number 3387062910, offset 0
correcting nextents for inode 28722524
bad data fork in inode 28722524
cleared inode 28722524
entry " qs " in shortform directory 28722525 references invalid inode 0
size of last entry overflows space left in in shortform dir 28722525, resetting to -2
entry contains offset out of order in shortform dir 28722525
....
Cheers,
F
P.S.
sorry for the double mail, Eric.
On Fri, May 10, 2013 at 12:39 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
--On Thu, May 09, 2013 at 07:22:32PM +0200, Filippo Stenico wrote:
> Hello,
> ran xfs_repair -vv -L -P -m1750 and segfault at expected point.Run it in gdb to get a stack trace of where it died.
>
> I got the core-dump with dbg symbols, along with repair output and strace
> output.
>
> What should I do with it? Provide as it is?
$ gdb xfs_repair corefile
...
> bt
and post the output, along with the repair output from the run that
crashed...
F
--
F
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
