All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andras Tantos <andras@tantosonline.com>
To: Phil Turmel <philip@turmel.org>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: How to recover after md crash during reshape?
Date: Thu, 29 Oct 2015 09:59:50 -0700	[thread overview]
Message-ID: <56325086.4060104@tantosonline.com> (raw)
In-Reply-To: <5630FB05.5070902@turmel.org>

Phil,

On 10/28/2015 9:42 AM, Phil Turmel wrote:
> If you stop the array cleanly and then manually re-assemble with 
> --update=metadata, you might get around it. (Specify all of the 
> devices explicitly to ensure you don't get burned by v0.90's problems 
> with last partitions.) You definitely don't want to stay on v0.90, but 
> you may need to for now to get out of trouble. Phil 

It seems that my mdadm doesn't have an --update=metadata option, which 
if I understand it right means I have to re-create the array with the 
no-bitmap option. How dangerous is that? Is it possible that things get 
overwritten during the re-create process in the data portion of the array?

I've read that GRUB (which is my bootloader) didn't support v1.0 
superblocks for a while. It seems that 0.99 version of GRUB (which is 
what I have) has it, but how to make certain? I don't want to render my 
system un-bootable...

Can you expand a little bit on the problems of v0.90 superblocks and why 
upgrading is advantageous? What I've read about the differences (lifted 
limit of number of devices/array and 2TB per device limit) don't really 
apply to my case.

Thanks,
Andras


  parent reply	other threads:[~2015-10-29 16:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  2:35 How to recover after md crash during reshape? andras
2015-10-20 12:50 ` Anugraha Sinha
2015-10-20 13:04 ` Wols Lists
2015-10-20 13:49 ` Phil Turmel
     [not found]   ` <3baf849321d819483c5d20c005a31844@tantosonline.com>
2015-10-20 15:42     ` Phil Turmel
2015-10-20 22:34       ` Anugraha Sinha
2015-10-21  3:52       ` andras
2015-10-21 12:01         ` Phil Turmel
2015-10-21 16:17       ` Wols Lists
2015-10-21 16:05         ` Phil Turmel
2015-10-25 14:15       ` andras
2015-10-25 23:02         ` Phil Turmel
2015-10-28 16:31           ` Andras Tantos
2015-10-28 16:42             ` Phil Turmel
2015-10-28 17:10               ` Andras Tantos
2015-10-28 17:38                 ` Phil Turmel
2015-10-29 16:59               ` Andras Tantos [this message]
2015-10-30 18:12                 ` Phil Turmel
2015-11-03 23:42                   ` How to recover after md crash during reshape? - SOLVED/SUMMARY Andras Tantos
2015-10-21  1:35 ` How to recover after md crash during reshape? Neil Brown
2015-10-21  4:03   ` andras
2015-10-21 12:18   ` Phil Turmel
2015-10-21 20:26     ` Neil Brown
2015-10-21 20:37       ` Phil Turmel

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=56325086.4060104@tantosonline.com \
    --to=andras@tantosonline.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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.