On Friday October 19, snitzer@xxxxxxxxx wrote: > > To further test this I used 2 local sparse 732456960K loopback devices > and attempted to create the raid1 in the same manner. It failed in > exactly the same way. This should cast further doubt on the bad block > theory no? Yes :-) > > I'm using a stock 2.6.19.7 that I then backported various MD fixes to > from 2.6.20 -> 2.6.23... this kernel has worked great until I > attempted v1.0 sb w/ bitmap=internal using mdadm 2.6.x. > > But would you like me to try a stock 2.6.22 or 2.6.23 kernel? Yes please. I'm suspecting the code in write_sb_page where it tests if the bitmap overlaps the data or metadata. The only way I can see you getting the exact error that you do get it for that to fail. That test was introduced in 2.6.22. Did you backport that? Any chance it got mucked up a bit? I did the loopback test on current -mm and it works fine. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
