Hi,
I''ve an utterly broken btrfs that makes btrfsck and btrfs-debug-tree
(version 0.19) die with a core dump. Are you interested in this
filesystem? Unfortunely, it has a size of 1TB and contains the backups of
our customers. Hence, I can''t publish it. How can we come together?
Core was generated by `btrfs-debug-tree /dev/sdd2''.
Program terminated with signal 6, Aborted.
(gdb) bt full
#0 0x00002aaefe0e9f55 in *__GI_raise (sig=<value optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
pid = <value optimized out>
selftid = <value optimized out>
#1 0x00002aaefe0ecd90 in *__GI_abort () at abort.c:88
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20},
sa_mask = {__val = {33796928, 24, 46931078315616, 4, 46931075322034,
46931078315616, 0, 46931074869936, 46931070637088, 46931078315616, 4294967295,
1, 0, 27266932, 14, 27041808}}, sa_flags = 4096, sa_restorer = 0x619220
<_GLOBAL_OFFSET_TABLE_+64>}
sigs = {__val = {32, 0 <repeats 15 times>}}
#2 0x000000000040c4bb in btrfs_print_tree (root=0x19ca010, eb=<value
optimized out>) at print-tree.c:662
next = 0x203a2e0
i = 14
nr = 64
size = 4096
disk_key = {objectid = 756658176, type = 168 ''\250'',
offset = 4096}
#3 0x000000000040c4c6 in btrfs_print_tree (root=0x19ca010, eb=<value
optimized out>) at print-tree.c:663
next = 0x1a00f10
i = 0
nr = 12
size = 4096
disk_key = {objectid = 902778220544, type = 168
''\250'', offset = 4096}
#4 0x0000000000412f3b in main (ac=<value optimized out>, av=<value
optimized out>) at debug-tree.c:263
buf = 0x19fddc0
skip = <value optimized out>
root = <value optimized out>
path = {nodes = {0x19fcd50, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, slots =
{0, 0, 0, 0, 0, 0, 0, 0}, locks = {0, 0, 0, 0, 0, 0, 0, 0}, reada = 0,
lowest_level = 0, search_for_split = 0, keep_locks = 0, skip_locking = 0,
leave_spinning = 0}
key = {objectid = 0, type = 132 ''\204'', offset = 0}
ri = {inode = {generation = 1, transid = 0, size = 3, nbytes = 4096,
block_group = 0, nlink = 1, uid = 0, gid = 0, mode = 16877, rdev = 0, flags = 0,
sequence = 0, reserved = {0, 0, 0, 0}, atime = {sec = 0, nsec = 0}, ctime = {sec
= 0, nsec = 0}, mtime = {sec = 0, nsec = 0}, otime = {sec = 0, nsec = 0}},
generation = 1124, root_dirid = 0, bytenr = 36537159680, byte_limit = 0,
bytes_used = 4096, last_snapshot = 0, flags = 0, refs = 1, drop_progress =
{objectid = 0, type = 0 ''\000'', offset = 0}, drop_level = 0
''\000'', level = 3 ''\003''}
leaf = 0x19fcd50
disk_key = {objectid = 2, type = 132 ''\204'', offset =
0}
uuidbuf =
"\000\000\000\000\000\000\000\000X3\313\375\256*\000\000p\b\242T\377\177\000\000\210\b\242T\377\177\000\000\000\000\000\000\001"
ret = <value optimized out>
slot = <value optimized out>
extent_only = 0
tree_root_scan = 0x19ca010
__PRETTY_FUNCTION__ = "main"
Core was generated by `btrfsck /dev/sdd2''.
Program terminated with signal 6, Aborted.
(gdb) bt full
#0 0x00002b7362f01f55 in *__GI_raise (sig=<value optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
pid = <value optimized out>
selftid = <value optimized out>
#1 0x00002b7362f04d90 in *__GI_abort () at abort.c:88
act = {__sigaction_handler = {sa_handler = 0, sa_sigaction = 0}, sa_mask
= {__val = {47774584400000, 41680688, 37266931712, 0, 0, 1, 47774581843675,
47774580959920, 47774576727072, 140736110625552, 4294967295, 47774584405704, 0,
41680688, 37266931712, 0}}, sa_flags = 0, sa_restorer = 0x61cbe0
<_GLOBAL_OFFSET_TABLE_+64>}
sigs = {__val = {32, 0 <repeats 15 times>}}
#2 0x000000000040b943 in btrfs_lookup_extent_info (trans=0x0, root=0x27bff30,
bytenr=37266931712, num_bytes=4096, refs=0x0, flags=0x7fffade18808) at
extent-tree.c:1453
path = <value optimized out>
ret = <value optimized out>
key = {objectid = 37266931712, type = 168 ''\250'',
offset = 4096}
item_size = <value optimized out>
num_refs = <value optimized out>
extent_flags = <value optimized out>
__PRETTY_FUNCTION__ = "btrfs_lookup_extent_info"
#3 0x0000000000402332 in run_next_block (root=0x27bff30) at btrfsck.c:2140
buf = 0x289a640
size = 4096
owner = 7
flags = <value optimized out>
nritems = <value optimized out>
key = {objectid = 18446744073709551606, type = 128
''\200'', offset = 123843641344}
ret = <value optimized out>
i = 0
cache = <value optimized out>
__PRETTY_FUNCTION__ = "run_next_block"
#4 check_extents (root=0x27bff30) at btrfsck.c:2428
extent_cache = {root = {rb_node = 0x27ddc90, rotate_notify = 0x6}}
seen = {root = {rb_node = 0x27ddd30, rotate_notify = 0}}
pending = {root = {rb_node = 0x27ff550, rotate_notify = 0}}
reada = {root = {rb_node = 0x28069c0, rotate_notify = 0x2b7362ac0e45
<_dl_runtime_resolve+53>}}
nodes = {root = {rb_node = 0x286ed60, rotate_notify = 0x3}}
path = {nodes = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, slots = {0, 0,
0, 0, 0, 0, 0, 0}, locks = {0, 0, 0, 0, 0, 0, 0, 0}, reada = 0, lowest_level =
0, search_for_split = 0, keep_locks = 0, skip_locking = 0, leave_spinning = 0}
key = {objectid = 0, type = 132 ''\204'', offset = 0}
found_key = {objectid = 18446744073709551607, type = 132
''\204'', offset = 0}
ret = <value optimized out>
last = 37266931712
leaf = <value optimized out>
ri = {inode = {generation = 1, transid = 0, size = 3, nbytes = 4096,
block_group = 0, nlink = 1, uid = 0, gid = 0, mode = 16877, rdev = 0, flags = 0,
sequence = 0, reserved = {0, 0, 0, 0}, atime = {sec = 0, nsec = 0}, ctime = {sec
= 0, nsec = 0}, mtime = {sec = 0, nsec = 0}, otime = {sec = 0, nsec = 0}},
generation = 5, root_dirid = 256, bytenr = 29380608, byte_limit = 0, bytes_used
= 4096, last_snapshot = 0, flags = 0, refs = 1, drop_progress = {objectid = 0,
type = 0 ''\000'', offset = 0}, drop_level = 0
''\000'', level = 0 ''\000''}
__PRETTY_FUNCTION__ = "check_extents"
#5 0x0000000000404acb in main (ac=<value optimized out>, av=<value
optimized out>) at btrfsck.c:2460
root = <value optimized out>
ret = 1
Bye, Jörg.
--
Du kannst einem Schwein einen goldenen Ring durch die Nase ziehen,
deswegen bleibt es trozdem ein Schwein!
Chris Mason
2010-Feb-17 14:11 UTC
Re: Broken btrfs; btrfsck and btrfs-debug-tree core dumps
On Tue, Feb 16, 2010 at 11:15:44AM +0100, Jörg Sommer wrote:> Hi, > > I''ve an utterly broken btrfs that makes btrfsck and btrfs-debug-tree > (version 0.19) die with a core dump. Are you interested in this > filesystem? Unfortunely, it has a size of 1TB and contains the backups of > our customers. Hence, I can''t publish it. How can we come together?I''m most interested in how it got corrupted. Was there a specific event that you think caused this? -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html