From: Wols Lists <antlists@youngman.org.uk>
To: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: Linux raid wiki
Date: Mon, 26 Sep 2016 22:37:49 +0100 [thread overview]
Message-ID: <57E9952D.6020703@youngman.org.uk> (raw)
In-Reply-To: <33ee0032-11a7-3637-170a-a9da94c7bda9@turmel.org>
On 26/09/16 22:19, Phil Turmel wrote:
> On 09/26/2016 12:44 PM, Wols Lists wrote:
>> The next section -
>>
>> https://raid.wiki.kernel.org/index.php/Assemble_Run
>>
>> addresses what to do if the array is messed up in some way. Would you
>> mind taking a look at that now too :-)
>
> Hmmm. The last bit is less than ideal. If all drives are faulty, but
> runnable in the array with at least one drive of redundancy, the best
> way to put good drives in service is one-by-one mdadm --replace. That
> lets the redundancy fix any errors, and doesn't load down the problem
> drive any more than ddrescue would. And it has the benefit of
> increasing reliability as you go.
>
> If you don't have any redundancy left, then ddrescue of all readable
> drives is reasonable.
>
Which is the state this page is meant to cover. I'm assuming that if you
get this far, you have at an absolute minimum had to have done a
"--force --assemble" just to get a working array.
Each page has been intended to successively cover the state of the array
getting worse. The next page is "my metadata is trashed - mdadm says the
drive doesn't exist". I'm really not sure how to tackle that, but I know
there are several threads which cover damaged or trashed superblocks. I
think I'll just have to say "this is how you track down a GPT. This is
how you track down a superblock. This is how you interpret it. Get the
experts to help you put the array together again."
Cheers,
Wol
prev parent reply other threads:[~2016-09-26 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 23:31 Linux raid wiki Wols Lists
2016-09-23 17:35 ` WNSDEV
2016-09-23 18:43 ` Wols Lists
2016-09-23 19:02 ` Peter Sangas
2016-09-24 3:38 ` Phil Turmel
2016-09-24 13:18 ` Wols Lists
2016-09-26 14:01 ` Phil Turmel
2016-09-26 16:44 ` Wols Lists
2016-09-26 21:19 ` Phil Turmel
2016-09-26 21:37 ` Wols Lists [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=57E9952D.6020703@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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.