All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Eddy Ilg|univation <eddy.ilg@univation.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovering RAID1 superblock
Date: Mon, 21 Jan 2013 21:09:20 +0000	[thread overview]
Message-ID: <50FDAE80.5090907@anonymous.org.uk> (raw)
In-Reply-To: <50FDA7E4.9010705@univation.de>

On 21/01/2013 20:41, Eddy Ilg|univation wrote:
> Dear linux-raid users,
>
> I have a disk of a 2-disk RAID1 array with damaged superblock. Please
> forgive me if this question as already been asked, but as I am afraid of
> executing a dangerous command, I need to ask:
>
> To recover the superblock, I would run
> mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sdb2 missing
>
> Is is correct, that this will NOT erase the data on /dev/sdb2?

As long as you're using the same mdadm version as the array was created 
with, and that is the create command used in the first place (apart from 
the "missing" bit of course), then yes.

If it's a different mdadm version, it may have a different default 
metadata type, so the new metadata might overwrite the original data area.

Different mdadm versions create arrays with different data offsets too, 
so even if the new create doesn't overwrite your old metadata, you may 
not be able to see your data (or at least, your filesystem may not be 
able to make sense of it).

So be sure to save a copy of `mdadm --examine /dev/sdb2` before you 
start, then check the man pages and release notes for the mdadm 
version(s) you're using.

Cheers,

John.


      reply	other threads:[~2013-01-21 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 20:41 Recovering RAID1 superblock Eddy Ilg|univation
2013-01-21 21:09 ` John Robinson [this message]

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=50FDAE80.5090907@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=eddy.ilg@univation.de \
    --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.