linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: John Stoffel <john@stoffel.org>, linux-raid@vger.kernel.org
Subject: Re: Recovering a RAID6 after all disks were disconnected
Date: Sat, 24 Dec 2016 09:50:26 +1100	[thread overview]
Message-ID: <87a8bmp8el.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAOxFTcwaDfK+gKX2d4L4DuX=pf273M8qKGGOo8G+iAVSxurHhA@mail.gmail.com>

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

On Sat, Dec 24 2016, Giuseppe Bilotta wrote:
>
>
> So the array assembles, and raid6check reports no error, but the data
> is actually inaccessible .. am I missing other aspects of the metadata
> that need to be restored?

Presumably, yes.

If you provide "mdadm --examine" from devices in both the "working" and
the "not working" case, I might be able to point to the difference.

Alternately, use "mdadm --dump" to extract the metadata, then "tar
--sparse" to combine the (sparse) metadata files into a tar-archive, and
send that.  Then I would be able to experiment myself.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2016-12-23 22:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  8:59 Recovering a RAID6 after all disks were disconnected Giuseppe Bilotta
2016-12-07 14:31 ` John Stoffel
2016-12-07 17:21   ` Giuseppe Bilotta
2016-12-08 19:02     ` John Stoffel
2016-12-22 23:11       ` Giuseppe Bilotta
2016-12-22 23:25         ` NeilBrown
2016-12-23 16:17           ` Giuseppe Bilotta
2016-12-23 21:14             ` Giuseppe Bilotta
2016-12-23 22:50               ` NeilBrown [this message]
2016-12-24 14:47                 ` Giuseppe Bilotta
2016-12-23 22:46             ` NeilBrown
2016-12-24 14:34               ` Giuseppe Bilotta

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=87a8bmp8el.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=john@stoffel.org \
    --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;
as well as URLs for NNTP newsgroup(s).