All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Claudiu Rad <jazzman@misalpina.net>, linux-raid@vger.kernel.org
Subject: Re: recovering failed and unrecognizable RAID5 during mdadm --grow without backup
Date: Fri, 13 May 2016 10:04:53 -0400	[thread overview]
Message-ID: <5735DF05.8080706@turmel.org> (raw)
In-Reply-To: <7cf56631-7909-6a92-f0b2-05dd02722ee8@misalpina.net>

On 05/12/2016 05:37 PM, Claudiu Rad wrote:

> how can i safely stop this reshape and assuming my / partition inside
> the array is sane enough restart the actual server normally after
> fsck-ing all volumes?

Well, your root is inside the array.  So you won't be able to boot
without the array assembling in the initramfs, which needs manual
intervention to supply the backup file.

If your hosting service provides access to the boot console, you could
do this with "rd.shell" or whatever kernel option tells your initramfs
to drop into a rescue console.  Then you could manually assemble and
resume booting.  This would be true even if you had properly specified a
backup file outside the array.

I suspect this was one of the motivations for the enhancement to modern
mdadm & kernels to avoid the backup file for many cases by manipulating
the data offset.  Such a reshape in progress can be automatically
assembled without special options during boot.  Plus it is faster -- one
third fewer I/O operations.

Phil

  parent reply	other threads:[~2016-05-13 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12  6:22 recovering failed and unrecognizable RAID5 during mdadm --grow without backup Claudiu Rad
2016-05-12 18:58 ` Phil Turmel
2016-05-12 20:09   ` Claudiu Rad-Lohanel
2016-05-12 20:23     ` Phil Turmel
     [not found]       ` <7cf56631-7909-6a92-f0b2-05dd02722ee8@misalpina.net>
2016-05-13 14:04         ` Phil Turmel [this message]
2016-05-13 14:11           ` Phil Turmel
2016-05-13 14:26             ` Claudiu Rad-Lohanel
2016-05-13 14:39               ` Andreas Klauer
2016-05-13 15:33                 ` Claudiu Rad-Lohanel

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=5735DF05.8080706@turmel.org \
    --to=philip@turmel.org \
    --cc=jazzman@misalpina.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 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.