All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: "Björn Augustsson" <oggust@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Reshape stuck immediately, backup file all nulls
Date: Sat, 30 Jan 2016 12:09:55 -0500	[thread overview]
Message-ID: <56ACEE63.6070108@turmel.org> (raw)
In-Reply-To: <CABRqA0i7bAB3Xca1a29u2JYOF2UaE_w1sY73se3menp+ExWWKA@mail.gmail.com>

Hi Björn,

On 01/30/2016 07:21 AM, Björn Augustsson wrote:

> The question is, what kind of state am in now? 

The kernel is waiting for mdmon (mdadm as a background task) to step
through the stripes.  mdmon died and the kernel will wait forever.

> And how should I recover?
> Will just adding a policy to allow access to that file, and then
> mdadm --grow --continue /dev/md127
> fix it? 

Probably.  Others have fixed this by disabling selinux for the reshape.
 Don't forget to specify --backup-file again on the command line.  (I
don't use selinux myself, so I can't be more specific.)

In the future, consider not using a backup file at all -- mdadm
generally leaves enough dead space on devices to avoid the need.

> Is the broken backup file going to be a problem?

Shouldn't be. Report back if it is.

Phil
--
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

  reply	other threads:[~2016-01-30 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 12:21 Reshape stuck immediately, backup file all nulls Björn Augustsson
2016-01-30 17:09 ` Phil Turmel [this message]
2016-01-31 14:59   ` Björn Augustsson
2016-02-01  1:02     ` George Rapp
2016-02-01 18:45       ` Björn Augustsson
2016-02-11  4:22   ` NeilBrown
2016-01-30 18:13 ` Mikael Abrahamsson

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=56ACEE63.6070108@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=oggust@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.