>> Looks like we're looping on a single block. What happens when you >> dmesg -n1 to cut down on the console traffic? >> > Nothing changes I still have endless repeats of > > parent transid verify failed on 1682586464256 wanted 285114 found 11257 > >> If that doesn't help we can change it to spit a stack trace to figure >> out where the looping is happening. We should be erroring out instead >> of hitting it over and over again. > > In my kernel noviceness i tried attaching gdb to the btrfs-endio-met, > however apparently you can't attach gdb to a kernel thread like that > If you could assist me in obtaining a call trace I will gladly attempt > to resolve the matter. Ok I had some free time and decided to excersice my googlefoo and came up with this trace parent transid verify failed on 3241193205760 wanted 285287 found 281382 Pid: 2163, comm: mount Not tainted 2.6.35-0.23.rc3.git6.fc14.x86_64 #1 Call Trace: [<ffffffffa047c376>] verify_parent_transid+0xb7/0xfe [btrfs] [<ffffffffa047c4f2>] btrfs_buffer_uptodate+0x49/0x59 [btrfs] [<ffffffffa04686a2>] read_block_for_search+0x8f/0x289 [btrfs] [<ffffffffa046d554>] btrfs_search_slot+0x3ae/0x513 [btrfs] [<ffffffffa0470ece>] btrfs_read_block_groups+0x73/0x526 [btrfs] [<ffffffff8149b0a3>] ? _raw_spin_unlock+0x2b/0x2f [<ffffffffa0469f56>] ? btrfs_root_node+0x2a/0x32 [btrfs] [<ffffffffa047d287>] ? find_and_setup_root+0xab/0xbc [btrfs] [<ffffffffa04800eb>] open_ctree+0xf19/0x143a [btrfs] [<ffffffffa0467960>] btrfs_get_sb+0x1ce/0x40b [btrfs] [<ffffffff810e9cfd>] ? free_pages+0x49/0x4e [<ffffffff8112c9f9>] vfs_kern_mount+0xbd/0x19b [<ffffffff8112cb3f>] do_kern_mount+0x4d/0xed [<ffffffff81143742>] do_mount+0x776/0x7ed [<ffffffff81143841>] sys_mount+0x88/0xc2 [<ffffffff81009c32>] system_call_fastpath+0x16/0x1b > Dan Kozlowski > > -- > S.D.G. > -- S.D.G. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
