On Wed, Oct 10, 2012 at 01:38:53PM -0600, Richard W.M. Jones wrote: > On Wed, Oct 10, 2012 at 08:38:08AM -0400, Chris Mason wrote: > > On Tue, Oct 09, 2012 at 03:00:12AM -0600, David Sterba wrote: > > > On Tue, Oct 09, 2012 at 08:33:57AM +0100, Richard W.M. Jones wrote: > > > > On Tue, Oct 09, 2012 at 08:20:02AM +0100, Richard W.M. Jones wrote: > > > > > On Mon, Oct 08, 2012 at 08:00:51PM -0400, Chris Mason wrote: > > > > > > Ok, what's a rough idea of the mainline git equiv of the buggy > > > > > > kernel? > > > > > > > > > > On my local machine, I'm reproducing this with what Fedora calls > > > > > 3.7.0-0.rc0.git2.4.fc19.x86_64 > > > > > > > > OK, that's not very helpful is it :-) AFAIK it should be possible > > > > to reproduce this with Linus's git kernel, but I haven't proven > > > > that yet. > > > > > > Found the same error message in my logs with master+next: > > > > > > Oct 8 15:07:25 kernel: [13048.856283] device fsid > > > cd15a893-e955-49cc-989c-4fd952a838a6 devid 1 transid 3 /dev/sda9 > > > Oct 8 15:07:25 kernel: [13048.866880] btrfs: disk space caching is > > > enabled > > > Oct 8 15:07:25 kernel: [13048.875767] btrfs: failed to recover relocation > > > Oct 8 15:07:25 kernel: [13048.884662] btrfs: open_ctree failed > > > > > > There are some xfstests that triggered the related bug with stale data, > > > I'm investigating further. > > > > Check your progs, this commit was updated to continue instead of break. > > > > https://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git;a=commitdiff;h=6eba9002956ac40db87d42fb653a0524dc568810;hp=bc130ecd0260e4ee6ffe07ae43fc90db281a4daa > > > > The original commit triggered those errors during 204. > > It does seem as if adding that commit to btrfs-progs fixes the > original bug I was reporting. As before, my test isn't very reliable, > so I cannot be 100% sure. I will continue running tests.
I didn't mention that one earlier because the git commit id in your progs version string never had the buggy commit. -chris -- 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
