On Oct 3, 2013, at 12:55 PM, Christopher Krooß <c.kro...@gmail.com> wrote:
> On Do, 2013-10-03 at 12:50 -0600, Chris Murphy wrote: >> On Oct 3, 2013, at 12:34 PM, Christopher Krooß <c.kro...@gmail.com> wrote: >> >>> Hi, I just encountered this kernel bug when I executed "btrfs balance start >>> /". I'm sorry if this is not enough data but I couldn't save the log as my >>> system didn't respond after the dmesg. It said "kernel bug" before the >>> trace. >>> >>> partial log: http://i.imgur.com/ygk3Nid.jpg >> >> If it's kernel 3.11.0 through 3.11.4 it may be a known problem. I don't know >> if it adversely affects the file system. I'd either look at 3.12.0-rc3, or >> regress to 3.10.14 if you need to balance sooner than later. Or wait until >> several balance related fixes end up in 3.11.x (maybe 3.11.5). >> >> If you aren't using a 3.11 kernel, it might be useful to know what version >> you are using. >> >> Chris Murphy > > > Thanks for the info. I'm in fact running 3.11.3 so I'll just wait it > out. There were some csum errors after I rebooted, but it seems to just > be /var/log/journal. Yes, avoid balance until there's a fix, and consider tossing the journals to remove the csum errors. This bug is fixed with this patch headed to stable. http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg27549.html 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
