Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Ben Bucksch <linux.news@bucksch.org>
To: Oliver Schinagl <oliver+list@schinagl.nl>
Cc: linux-raid@vger.kernel.org
Subject: Re: md RAID5: Disk wrongly marked "spare", need to force re-add it
Date: Mon, 15 Apr 2013 03:34:04 +0200	[thread overview]
Message-ID: <516B590C.5060807@bucksch.org> (raw)
In-Reply-To: <516B3077.9020507@schinagl.nl>

Hey Oliver,

first off: thanks for trying to help me.

Oliver Schinagl wrote, On 15.04.2013 00:40:
> Firstly, have you written anything TOO the array while resyncing? If 
> not, chances are your array is in a reasonable shape still.

I did write to the array (in fact, I did a bonnie++, which in 
retrospective is very stupid, and I'm upset I did it, but hindsight is 
20/20 - I assumed the array was fine at that time), BUT if you look at 
the "event count" of each drive, the sdl marked "spare" has an event 
count just 2 lower then all the others, so they are very close.

> Now check the event count for all your drivers and compare. If the 
> 'broken' drive is only a few off (1 or 2 I think i spotted below, try 
> the following) 

Exactly.

> The 'spare' drive, I don't know what its status is.

According to SMART, it's just fine. Its event status is very close to 
the others.

> Theoretically, I would assume that the resync the data written to the 
> disk is exactly the same as it was before, so keep that in mind as a 
> last resort.

Yes, that's my plan. My question is: HOW can I tell mdadm to use it?

> mdadm --run --force -A /dev/md0 /dev/sd...

I've tried that, and it tells me the array can't be started, because I 
have RAID 5 with 8 drives (in normal situation), 6 good drives, and 2 
spares (1 working fine, 1 with hardware failure). So, after this 
command, I end up in "inactive" operation mode.

> Now the broken drive. Check your cables!! and run smartctl on it to 
> give smart a chance to 'fix' the drive somewhat and check its 
> status/health. ...
> If it fails again (at 80% because of hardware failure) you can't 
> re-use the broken disk. It really is broken :p

It failed twice during resync, at around the same point, and smartctl 
tells me it's broken, so I assume it's gone for good. (Also, the failed 
drive is also marked as "spare" currently.)

> your very last hope, is to not use the broken drive, and 'force' the 
> above using the earlier marked spare.

How? I haven't managed to do that, that's my whole question.


  reply	other threads:[~2013-04-15  1:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 20:08 md RAID5: Disk wrongly marked "spare", need to force re-add it Ben Bucksch
2013-04-13 14:19 ` Roy Sigurd Karlsbakk
2013-04-14 22:40 ` Oliver Schinagl
2013-04-15  1:34   ` Ben Bucksch [this message]
2013-04-14 17:30     ` Oliver Schinagl
2013-04-15 10:26       ` Ben Bucksch
2013-04-14 18:16         ` Oliver Schinagl
2013-04-18 13:17         ` Ben Bucksch
2013-04-18 13:58           ` Maarten
2013-04-19 22:56             ` linux.news
2013-04-20  1:26               ` Ben Bucksch
2013-04-20  1:53                 ` Ben Bucksch
2013-04-21  7:23                   ` Brad Campbell
2013-04-21  8:20                     ` Ben Bucksch
2013-04-21 10:45                       ` Brad Campbell
2013-04-21 18:17                         ` Phil Turmel
2013-04-21 22:00                           ` Ben Bucksch
2013-04-21 11:07                       ` Roy Sigurd Karlsbakk
2013-04-21 21:50                   ` NeilBrown
2013-04-21 21:46                 ` NeilBrown
2013-04-18 14:18           ` Roy Sigurd Karlsbakk
2013-04-18 14:38           ` Robin Hill
2013-04-20 13:44             ` Oliver Schinagl

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=516B590C.5060807@bucksch.org \
    --to=linux.news@bucksch.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=oliver+list@schinagl.nl \
    /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