> > > I eventually got a kernel panic when copying large amounts of data to a > > > [degraded] raid6 array, which this time was the full 600 GB size. > > > Don't know if it is helpful to anyone but info below: > > > > The panic is from reiserfs, and it's occuring because the FS is > > getting corrupted due to the raid6 problems. > > It's still very odd to me that so far the only thing that triggers > this kind of problems is reiserfs. Either reiserfs just has a really > odd series of access patterns, or it is relying on behaviour which > isn't actually guaranteed. I suspect the former, but it's still odd. No, I did see the same corruption with XFS; it just took more work before it would show up (ie. I couldn't get it to show up by simply copying one huge file; I had to untar a full filesystem onto it). So I would suspect the odd access patterns. I could also run a test with EXT2/3 if you'd like. I didn't manage to trigger the corruption directly on the md device, but my access pattern was quite simple in that case (dd big blocks to different areas). Are you able to reproduce the problem with the scripts I sent earlier? If not, I can give you access to a machine that can. -jim - 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
