Just reproduced it - raid10 did the trick. I'll try and debug it this weekend. On Tue, Nov 29, 2011 at 12:45 AM, Kent Overstreet <koverstreet@xxxxxxxxxx> wrote: > On Tue, Nov 29, 2011 at 04:30:22PM +0800, Brad Campbell wrote: >> On 29/11/11 15:54, Kent Overstreet wrote: >> >Ok, that's weird. It shouldn't be able to register the second time >> >because the first register opens it exclusively, and the second open >> >will fail with -EBUSY. >> >> Can reproduce it at will here. > > I don't doubt you, just surprised. I'll try it out first thing tomorrow. > No reason I shouldn't be able to reproduce it. > >> I doubt its the driver as the RAID is on the same card as the single >> drive I tested with last time. > > Ok, raid10 is the one I didn't test - I tried raid0 and 6 and those > worked, but each raid layer has its own code to process bios so it > sounds like there's a corner case we're tripping. > >> I can probably try some other RAID levels this evening if it would >> help. I trashed the RAID recently anyway so I need to re-build it >> from scratch. > > Let me see if I can reproduce it first, I'll try it first thing in the > morning. Hopefully it'll be something easy. > > Were you running in passthrough mode or was caching on when you got the > oops? -- 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
