On Fri, Dec 11 2015, George Rapp wrote: > > I appear to be too early in the reshape for auto-recovery, but too far > along to just say "never mind on that whole reshape business". Any > other thoughts? > What this means is that you've hit a corner case that was never thought through properly and isn't handled correctly. The current state of the array is (I think) that it looks like a reshape to reduce the number of devices in the array has very nearly completed. Only the first stripe needs to be completed. Whether that first stripe is still in the old "N+1" device layout or the new "N" device layout is unknown to the kernel - this information is only in the backup file (which doesn't exist). By telling mdadm --invalid-backup, you effectively tell mdadm that there is nothing useful in the backup file so it should know that the reshape has actually completed. But it has no way to tell the kernel that. What it should do in this case is (I think) rewrite the metadata to record that the reshape is complete. But it doesn't. I shouldn't be too hard to fix, but it isn't trivial either and I'm unlikely to get anywhere before the Christmas break. If you can get reshape to work at all (disable selinux?) you could try --update=revert-reshape and let the reshape to more devices progress for a while, and then revert it. If you cannot get anywhere, then use "mdadm --dump=/tmp/whatever /dev/mdthing" to create a copy of the metadata in some spares files. Then tar those up (a compressed tarchive should be tiny) and email them. Then I can try and see if I can make something work on exactly the array you have. NeilBrown
Attachment:
signature.asc
Description: PGP signature
