On 26.07.2011 12:12, Jan Schubert wrote: > On 07/26/2011 12:04 PM, Jan Schmidt wrote: >> On 25.07.2011 17:58, Jan Schubert wrote: >>> btrfs: unable to fixup at 182245531648 >>> btrfs: unable to fixup at 182245535744 >>> btrfs: unable to fixup at 182245539840 >> This is due to rate limitation of printk() to prevent flooding. I'd like >> to continue discussion of this problem on the list, but I didn't reply >> to the list this time due to the debug-tree link you gave me. > > OK, go on Jan, no problem. Is there any chance to use the numbers above > to identify related files?
Thanks for sending the debug-tree output. Turns out that there is a quite obvious bug in my code for extents that have refs but no inline ref at all. I'll fix this up and send a new version (hooray). Jan: It would be nice if you could try the new patch set once I've sent it. I don't need any additional input from you at the moment. Chris: As you suggested, the new version will also include two separate size fields in struct btrfs_data_container, which then can both be unsigned. -Jan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
