On Jun 27, 2014, at 9:14 AM, Rich Freeman <r-bt...@thefreemanclan.net> wrote:
> On Fri, Jun 27, 2014 at 9:06 AM, Duncan <1i5t5.dun...@cox.net> wrote: >> Hopefully that problem's fixed on 3.16-rc2+, but as of yet there's not >> enough 3.16-rc2+ reports out there from folks experiencing issues with >> 3.15 blocked tasks to rightfully say. > > Any chance that it was backported to 3.15.2? I'd rather not move to > mainline just for btrfs. The backports don't happen that quickly. I'm uncertain about specifics but I think many such fixes need to be demonstrated in mainline before they get backported to stable. > > I got another block this morning and failed to capture a log before my > terminals gave out. I switched back to 3.15.0 for the moment, and > we'll see if that fares any better. Yeah I'd start going backwards. The idea of going forwards is to hopefully get you unstuck or extract data where otherwise you can't, it's not really a recommendation for production usage. It's also often useful if you can reproduce the block with a current rc kernel and issue sysrq+w and post that. Then do your regression with an older kernel. 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
