On 9/19/16 4:06 PM, admin wrote:
> Hi *,
>
> so i got some problems using xfs_repair. (xfs_repair version 4.8.0-rc1)
>
> xfs_repair /dev/mapper/daten
> ####
> Phase 6 - check inode connectivity...
> reinitializing root directory
> reinitializing realtime bitmap inode
> reinitializing realtime summary inode
> - resetting contents of realtime bitmap and summary inodes
> - traversing filesystem ...
> bad hash table for directory inode 16384 (no data entry): rebuilding
> rebuilding directory inode 16384
> bad hash table for directory inode 16387 (no data entry): rebuilding
> rebuilding directory inode 16387
> - traversal finished ...
> - moving disconnected inodes to lost+found ...
> disconnected dir inode 16384, moving to lost+found
> Segmentation fault
>
> Strace output doesn't help me either:
> 1472 <... futex resumed> ) = 0
> 1472 munmap(0x7f806d865000, 8392704) = 0
> 1472 write(2, " - traversal finished ..."..., 33) = 33
> 1472 write(2, " - moving disconnected in"..., 55) = 55
> 1472 write(2, "disconnected dir inode 16384, ", 30) = 30
> 1472 write(2, "moving to lost+found\n", 21) = 21
> 1472 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x10000003f} ---
> 1472 +++ killed by SIGSEGV +++
>
>
> Any advice on how to proceed from there?
Either provide a debug binary + the core file, or run it through
valgrind, or better yet, do:
# xfs_metadump /dev/mapper/daten metadump.img
# bzip2 metadump.img
and provide the resulting bzip2'd file to me off-list, and I can probably
reproduce the problem and take a look at the bug.
Thanks,
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
