Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: "Jonathan Harker (Jesusaurus)" <jesusaurus@gentlydownthe.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help recovering an interrupted raid0 reshape
Date: Tue, 7 Apr 2015 16:30:04 +1000	[thread overview]
Message-ID: <20150407163004.7550da77@notabene.brown> (raw)
In-Reply-To: <CAC_83AFo47Zfe7rMqro7_k8dR-xpMcfiwQA7a9DTKpKPuHr=fA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]

On Mon, 6 Apr 2015 22:14:56 -0700 "Jonathan Harker (Jesusaurus)"
<jesusaurus@gentlydownthe.net> wrote:

> On Mon, Apr 6, 2015 at 6:50 PM, NeilBrown <neilb@suse.de> wrote:
> > On Tue, 7 Apr 2015 09:46:08 +1000 NeilBrown <neilb@suse.de> wrote:
> >
> >> On Fri, 3 Apr 2015 19:22:15 -0700 "Jonathan Harker (Jesusaurus)"
> >> <jesusaurus@gentlydownthe.net> wrote:
> >>
> >> >
> >> > Third, is it possible to resume the reshape? If not, can it be reverted?
> >> >
> >>
> >> I'll have to get back to you on that.  Hopefully you can be patient a little
> >> longer.
> >>
> >> NeilBrown
> >>
> 
> Thanks for taking the time to look into this. I've managed to be
> patient with the problem for about a week now (I was cautiously poking
> and prodding the array for a few days before reaching out to this
> list) so I think I can manage a little more patience.
> 
> >>
> >
> > Hi again Jonathan,
> >  please report what version of mdadm and of Linux that you are running.
> 
> My mdadm version is "mdadm - v3.3.1 - 5th June 2014" and my linux
> version (according to `uname -r`) is 3.16.2-3.
> 
> >
> > Also is there any chance that you tried
> >    mdadm --assemble .... --update=revert-reshape
> > ??
> > And if you did, why didn't you say so :-)
> 
> During those first couple days I tried a couple assemble and
> incremental commands to try to get the reshape to restart, though I
> don't remember exactly what they were. It's possible I tried something
> as scary and irreversible as --update=revert-reshape in some desperate
> haze, so let's assume I did, but I was trying hard to avoid any advice
> that included --force in the command.

Try:
  mdadm -S /dev/md124
  mdadm -A /dev/md124 --update=revert-reshape /dev/md/alpha /dev/md/beta
  mdadm -S /dev/md124
  mdadm -A /dev/md124 -vvv /dev/md/alpha /dev/md/beta /dev/md/gamma

What does that report?

NeilBrown


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  reply	other threads:[~2015-04-07  6:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04  2:22 Help recovering an interrupted raid0 reshape Jonathan Harker (Jesusaurus)
2015-04-06 23:46 ` NeilBrown
2015-04-07  1:50   ` NeilBrown
2015-04-07  5:14     ` Jonathan Harker (Jesusaurus)
2015-04-07  6:30       ` NeilBrown [this message]
2015-04-07 17:02         ` Jonathan Harker (Jesusaurus)
2015-04-07 21:13           ` NeilBrown
2015-04-07 22:31             ` Jonathan Harker (Jesusaurus)
2015-04-07 22:56               ` NeilBrown
2015-04-07 23:24                 ` Jonathan Harker (Jesusaurus)
2015-04-08  2:09                   ` NeilBrown
2015-04-08 17:00                     ` Jonathan Harker (Jesusaurus)

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=20150407163004.7550da77@notabene.brown \
    --to=neilb@suse.de \
    --cc=jesusaurus@gentlydownthe.net \
    --cc=linux-raid@vger.kernel.org \
    /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