On Thu, Jul 28, 2016 at 11:34:58PM +0300, Anatoly Pugachev wrote: > well, I think mkfs.btrfs is fixed, since I just tested it with :
Good news, thanks. > Not sure what we need to do with sparc64 btrfs module TPC messages. > Probably fill kernel bugzilla report? Yes please. > [1] http://u163.east.ru/btrfs/xfstests-btrfs-06x-results.tar.gz > [2] http://u163.east.ru/btrfs/kernel-4.7.0+-logs-xfstests-06x.txt.gz quick stats of the TPC messages: 23 __btrfs_map_block+0x36c/0x1180 9 __remove_rbio_from_cache+0x38/0x140 6 lock_stripe_add+0xb0/0x360 4 __btrfs_map_block+0x3d4/0x1180 3 __btrfs_map_block+0xca0/0x1180 running in 'gdb btrfs.ko' for each of the addresses should tell us what are the locations: gdb> l *(__btrfs_map_block+0x36c) ... Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
