I just went ahead and backed out the problematic change. Haven't even tried building the code yet - but if you feel lucky, it's up. I bet it fixes it. On Wed, Aug 29, 2012 at 1:56 AM, Kent Overstreet <koverstreet@xxxxxxxxxx> wrote: > On Mon, Aug 27, 2012 at 3:06 PM, Joseph Glanville > <joseph.glanville@xxxxxxxxxxxxxx> wrote: >> The issue is probably in fs/bio.c, some of the bio splitting changes >> could effect md without even having bcache in use. >> >> Kent, I will try get a test box up running more recent code then the >> stuff we run (which doesn't have said issue). > > Well, sounds like it's definitively just raid10 that triggers it - > that helps a lot. I think I know a sure workaround for it now, I'll > try and upload a new version tomorrow that should fix it. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
