On Sat, Mar 12 2016, Another Sillyname wrote: > Neil > > Thanks for the insight, much appreciated. > > I've tried what you suggested and still get stuck. > >>:losetup /dev/loop0 /tmp/foo/sdb1 >>:losetup /dev/loop1 /tmp/foo/sdc1 >>:losetup /dev/loop2 /tmp/foo/sdd1 >>:losetup /dev/loop3 /tmp/foo/sde1 >>:losetup /dev/loop4 /tmp/foo/sdf1 >>:losetup /dev/loop5 /tmp/foo/sdg1 >>:losetup /dev/loop6 /tmp/foo/sdh1 > > >>:mdadm --assemble --force --update=revert-reshape --invalid-backup /dev/md127 /dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 > mdadm: /dev/md127: Need a backup file to complete reshape of this array. > mdadm: Please provided one with "--backup-file=..." > mdadm: (Don't specify --update=revert-reshape again, that part succeeded.) > > As you can see it 'seems' to have accepted the revert command, but > even though I've told it the backup is invalid it's still insisting on > the backup being made available. > > Any further thoughts or insights would be gratefully received. Try giving it a backup file too. It doesn't matter what the contents of the file are because you have told it the file is invalid. But I guess it thinks it might still need a file to write new backups to temporarily. NeilBrown
Attachment:
signature.asc
Description: PGP signature
