Hello, It's been quiet on this issue to date and I assume everyone's working on important fixes and features etc - my apologies for the annoyance however at this point I'm looking for some collective guidance on my next move as I can't leave things in this state. To summarize, I am attempting to grow a RAID6 array from 6 to 7x 2TB disks however the reshape is stalling at 87.9% and throwing 'compute_blocknr: map not correct' errors. The system still responds but needs a hard reset to do anything MD related. I've tried varying kernel and mdadm versions all with the same result: 2.6.31, 2.6.33, 2.6.34-rc3 & rc4, each with mdadm 2.6.8, 3.0.2 & 3.1.2. The only kernel source file containing this string is drivers/md/raid5.c so I'm in the right place. So I am asking you fellow linux-raid'ers, what can be done in this situation ? I've filed a bug on bugzilla and now would only like to know if this issue has been experienced by others, if perhaps a fix is in the pipeline and any tips, tricks etc that may get the reshape completed then the data accessible again. I can see the only other non-destructuve option right now is to pull out the disks, restore from backup onto a new array & wait for a future kernel / mdadm version which will allow completion of the reshape. Cheers, Brett. -- 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
