All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm RAID6 "active" with spares and failed disks; need help
Date: Mon, 12 Jan 2015 16:35:57 +0000	[thread overview]
Message-ID: <54B3F7ED.1000809@youngman.org.uk> (raw)
In-Reply-To: <54B305B2.6000702@lentijn.sess.ink>

On 11/01/15 23:22, Valentijn Sessink wrote:
> Also, I would not have dared to run all these statements on "live" (or
> dead, for that matter ;-) disks.

I'm no expert either, but looking at the blog, I'm worried he might have
trashed the array with almost the first thing he did :-(

"add" says it will add a drive as spare if it didn't originally belong
to the array. If it adds a spare to a degraded array, the array will
immediately start to repair itself.

OOPS!!! As it sounds like exactly this could have happened - mdadm
didn't recognise the disk as it added it.

Just speculating, but unfortunately this seems quite likely :-(

Cheers,
Wol

  reply	other threads:[~2015-01-12 16:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54ABEE54.6020707@sympatico.ca>
2015-01-07 13:34 ` mdadm RAID6 "active" with spares and failed disks; need help Matt Callaghan
2015-01-11 20:26   ` Matt Callaghan
2015-01-11 23:22     ` Valentijn Sessink
2015-01-12 16:35       ` Wols Lists [this message]
2015-01-21  0:34         ` Matt Callaghan
2015-01-22  9:47           ` Valentijn
2015-03-27 23:48             ` Matt Callaghan
2015-03-28  1:59               ` Phil Turmel
2015-03-28 10:11                 ` Roman Mamedov
2015-03-28 15:11                   ` Read-only mounts (was mdadm RAID6 "active" with spares and failed disks; need help) Phil Turmel
     [not found]                 ` <55161943.1090206@sympatico.ca>
     [not found]                   ` <BLU436-SMTP135A84B36120ACD11B2783D81F70@phx.gbl>
2015-03-28 17:40                     ` mdadm RAID6 "active" with spares and failed disks; need help Phil Turmel
2015-01-06 14:16 Matt Callaghan

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=54B3F7ED.1000809@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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.