On Nov 5, 2013, at 7:34 AM, Hugo Mills <h...@carfax.org.uk> wrote: > On Tue, Nov 05, 2013 at 07:26:54AM -0700, Chris Murphy wrote: >> >> On Nov 5, 2013, at 5:16 AM, Russell Coker <russ...@coker.com.au> wrote: >>> >>> I presume that my filesystem is still corrupt. >> >> I'm the original reporter of the bug. The file system itself isn't corrupt, >> but the affected files probably are. In my case, systemd journal files were >> reported as corrupt by systemd following a balance, as well as btrfs scrub. >> Upon scrub, dmesg contains a path for each affected file. Upon deleting >> those files, subsequent scrubs come up clean. >> >> Fedora merged the fix for this bug with: 3.11.5-302.fc20, 3.11.6-200.fc19, >> 3.11.6-101.fc18. I thought for sure it was marked for stable to go into >> mainline 3.11.6, so somehow it's been missed. > > Someone else tripped over it on IRC last night, and I was surprised > to discover it hadn't made it upstream yet. :(
I just checked kernel.org changelogs and I'm not seeing this fixed in either 3.11.7 or 3.11.8. It is listed in today's git pull by Chris for 3.12 as Btrfs: relocate csums properly with prealloc extents Chris Murphy-- 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
