From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Shenkin Subject: Re: Raid-6 cannot reshape Date: Tue, 7 Apr 2020 11:25:13 +0100 Message-ID: <945332b3-6a47-c2b3-7d1e-70a44f6fd370@shenkin.org> References: <24a0ef04-46a9-13ee-b8cb-d1a0a5b939fb@shenkin.org> <6b9b6d37-6325-6515-f693-0ff3b641a67a@shenkin.org> <3135fb29-cfaa-d8ac-264d-fd3110217370@shenkin.org> <5E8B5865.9060107@youngman.org.uk> <08d66411-5045-56e1-cbad-7edefa94a363@turmel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <08d66411-5045-56e1-cbad-7edefa94a363@turmel.org> Content-Language: en-US Sender: linux-raid-owner@vger.kernel.org To: Phil Turmel , Wols Lists , Roger Heflin Cc: Linux-RAID List-Id: linux-raid.ids On 4/6/2020 9:34 PM, Phil Turmel wrote: > On 4/6/20 12:27 PM, Wols Lists wrote: >> On 06/04/20 17:12, Roger Heflin wrote: >>> When I looked at your detailed files you sent a few days ago, all of >>> the reshapes (on all disks) indicated that they were at position 0, so >>> it kind of appears that the reshape never actually started at all and >>> hung immediately which is probably why it cannot find the critical >>> section, it hung prior to that getting done.   Not entirely sure how >>> to undo a reshape that failed like this. >> >> This seems quite common. Search the archives - it's probably something >> like --assemble --revert-reshape. > > Ah, yes.  I recall cases where mdmon wouldn't start or wouldn't open the > array to start moving the stripes, so the kernel wouldn't advance. > SystemD was one of the culprits, I believe, back then. Thanks all. So, is the following safe to run, and a good idea to try? mdadm --assemble --update=revert-reshape /dev/md127 /dev/sd[a-g]3 And if that doesn't work, add a force? mdadm --assemble --force --update=revert-reshape /dev/md127 /dev/sd[a-g]3 And adding --invalid-backup if it complains about backup files? Thanks, Allie