linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Alexander Shenkin <al@shenkin.org>,
	Wols Lists <antlists@youngman.org.uk>,
	Roger Heflin <rogerheflin@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Raid-6 cannot reshape
Date: Tue, 7 Apr 2020 07:28:15 -0400	[thread overview]
Message-ID: <b9bb796e-08cd-e10a-d345-992e5f3abea7@turmel.org> (raw)
In-Reply-To: <945332b3-6a47-c2b3-7d1e-70a44f6fd370@shenkin.org>

Hi Allie,

On 4/7/20 6:25 AM, Alexander Shenkin wrote:
> 
> 
> 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

Yes.

> And if that doesn't work, add a force? >
> mdadm --assemble --force --update=revert-reshape /dev/md127 /dev/sd[a-g]3

Yes.

> And adding --invalid-backup if it complains about backup files?

Yes.

> Thanks,
> Allie

Phil

  reply	other threads:[~2020-04-07 11:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 10:16 Raid-6 cannot reshape Alexander Shenkin
     [not found] ` <6b9b6d37-6325-6515-f693-0ff3b641a67a@shenkin.org>
2020-04-06 15:27   ` Alexander Shenkin
2020-04-06 16:12     ` Roger Heflin
2020-04-06 16:27       ` Wols Lists
2020-04-06 20:34         ` Phil Turmel
2020-04-07 10:25           ` Alexander Shenkin
2020-04-07 11:28             ` Phil Turmel [this message]
2020-04-07 11:46               ` Alexander Shenkin
2020-04-07 12:28                 ` Phil Turmel
2020-04-07 12:31                   ` Phil Turmel
2020-04-07 13:19                     ` Alexander Shenkin
2020-04-07 15:08                       ` antlists
2020-04-07 17:04                         ` Alexander Shenkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b9bb796e-08cd-e10a-d345-992e5f3abea7@turmel.org \
    --to=philip@turmel.org \
    --cc=al@shenkin.org \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=rogerheflin@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).