From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: hung grow Date: Tue, 10 Oct 2017 09:06:42 -0400 Message-ID: <0d4987d9-e8ff-0cdb-6e45-7f962b75c189@turmel.org> References: <7e23d39b-aebb-0852-c98f-758bd99d3eb9@turmel.org> <89992d1f-172f-9fc6-3a1e-50df34e11d3b@turmel.org> <87po9xyv0r.fsf@notabene.neil.brown.name> <87d15xymgc.fsf@notabene.neil.brown.name> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-GB Sender: linux-raid-owner@vger.kernel.org To: Curt , NeilBrown Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids On 10/10/2017 08:08 AM, Curt wrote: > On Mon, Oct 9, 2017 at 8:41 AM, Curt wrote: >> On Mon, Oct 9, 2017 at 12:28 AM, NeilBrown wrote: >>> What happens if you run the --assemble --update=revert-reshape command on >>> these 6 devices (without --force)?? >> >> Here's the output >> mdadm --assemble --verbose --update=revert-reshape /dev/md127 >> /dev/sda1 /dev/sdc1 /dev/sdd1 /dev/sdb /dev/sdg1 /dev/sdz1 >> mdadm: looking for devices for /dev/md127 >> mdadm: Reshape position is not suitably aligned. >> mdadm: Try normal assembly and stop again >> > > What are the steps I need to take to resume the grow, but just enough > to get it to the point I can revert it and see what data I have on the > drives? Or can I force the revert? I'm stumped. Since your reshape position, while "0%", was 4GB into your array, there's no way to use --create --assume-clean to fix this. Unless Neil knows some magic, your data is toast. Sorry. Phil