> > I've never seen this before, and don't have time at the moment > to read the code to understand what it means. I did a search and here's the comment before the code I found spits out that error message. I don't know if it's useful to you /* reshape_position is a little messy. * Its value must be a multiple of the larger * chunk size, and of the "after" data disks. * So when reverting we need to change it to * be a multiple of the new "after" data disks, * which is the old "before". * If it isn't already a multiple of 'before', * the only thing we could do would be * copy some block around on the disks, which * is easy to get wrong. * So we reject a revert-reshape unless the * alignment is good. */ if (reshape_sectors % reshape_chunk) That doesn't read good for me. > > > Probably. But yeah, "fit state". That's the magic. /-: > What are the chances if I just do an assemble and let it try to grow again that it will complete without issue? Then assuming it completes, that I will have most my data still? Cheers, Curt -- 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
