On 2016-08-06 00:40, Chris Mason wrote:
Too big for the known problem though. Still, can you
btrfs-debug-tree
and just make sure it doesn't have inline items?
Hmmm....
# btrfs-debug-tree /dev/xvdb > /root/debug.tree
parent transid verify failed on 355229302784 wanted 49943295 found
49943301
parent transid verify failed on 355229302784 wanted 49943295 found
49943301
Ignoring transid failure
parent transid verify failed on 355233251328 wanted 49943299 found
49943303
parent transid verify failed on 355233251328 wanted 49943299 found
49943303
Ignoring transid failure
print-tree.c:1105: btrfs_print_tree: Assertion failed.
btrfs-debug-tree[0x418d99]
btrfs-debug-tree(btrfs_print_tree+0x26a)[0x41acf6]
btrfs-debug-tree(main+0x9a5)[0x432589]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f2369de0f45]
btrfs-debug-tree[0x4070e9]
Looks like the FS is mounted?
It is mounted, yes. Does btrfs-debug-tree need an unmounted FS?
I'm not able to unmount it unfortunately (in sense, the system has to
work).
Tomasz Chmielewski
https://lxadm.com
--
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
