From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: hung grow Date: Tue, 10 Oct 2017 14:06:45 -0400 Message-ID: <5a3fb3ec-299a-67c9-9d1c-ef28ca2164dd@turmel.org> References: <89992d1f-172f-9fc6-3a1e-50df34e11d3b@turmel.org> <87po9xyv0r.fsf@notabene.neil.brown.name> <87d15xymgc.fsf@notabene.neil.brown.name> <0d4987d9-e8ff-0cdb-6e45-7f962b75c189@turmel.org> <3e5766b0-1437-2857-4806-264386d1633f@youngman.org.uk> <6d4b7055-c26c-951e-b63c-273a7fe447b8@turmel.org> 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 Cc: Anthony Youngman , NeilBrown , linux-raid@vger.kernel.org List-Id: linux-raid.ids On 10/10/2017 10:23 AM, Curt wrote: >> >> Yeah, try without the revert. You don't have to wait for the reshape to >> finish to grab your critical files off of it. In fact, you might want >> to freeze the reshape to minimize the chance of hitting a not-yet-found URE. > > Ok, so try the before command, but instead of --update=revert-reshape, > do a --update=freeze-reshape? > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Just --freeze-reshape, not --update.