linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Iliev <daniel.iliev@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: raid10 problem with spare disk
Date: Mon, 10 Aug 2009 10:14:57 +0300	[thread overview]
Message-ID: <20090810101457.0390d92a.daniel.iliev@gmail.com> (raw)
In-Reply-To: 4340507aed0605af55fbaf1f9f694cfb.squirrel@neil.brown.name

On Sun, 9 Aug 2009 20:43:34 +1000 (EST)
"NeilBrown" <neilb@suse.de> wrote:
> 
> The remaining drives: sdb and sdd, are slot '0' and '1' though I suspect
> you expected them to be '1' and '3'.
> As they are 0 and 1, they don't provide all of the data.
> You need to figure out which slot sdc3 used to occupy and recreate
> the array using 'missing' for the fourth drive and '--assume-clean'
> to avoid resync.
>  e.g. mdadm -S /dev/md2
>       mdadm --create /dev/md2 --level 10 --layout f2 --assume-clean \
>                 /dev/sdb3 /dev/sdd3 missing /dev/sdc3
> That is assuming that you figure out that sdc3 was slot '3' (counting
> from 0).
> 
> The only way I can think of to find out where sdc3 was slot 2 or
> slot 3 is to try each of them and then run a 'check' and see what
> the mismatch count is.
> 
> So run the above --create command, but don't fsck or mount or anything
> else to the device.
> Then    echo check > /sys/block/md2/md/sync_action
> and watch the value of
>             /sys/block/md2/md/mismatch_cnt
> 
> if that keeps getting big, the we picked the wrong slot.
> If it stays fairly small (maybe a few hundred) then we probably got the
> right slot.
> To try the other arrangement, use the same command except for the last
> two words which should be swapped:   /dev/sdc3 missing
> 
> Once you have the array working again with 3 disks, choose a disk
> to remove that will leave the array still functional.  For a 4 disk
> raid10 in f2, you need either both even devices (0 and 2) or both
> odd devices (1 and 3).
> 
> Then continue with your original plan.
> --re-add should work if you have picked the right drive and have a
> bitmap.
> 
> 
> Good luck.
> 
> NeilBrown
> 

It worked. BIG THANKS!

The working combination was:

mdadm --create /dev/md2 --level 10 --layout f2 -c 4096 --assume-clean \
--raid-devices 4 /dev/sdb3 /dev/sdd3 missing /dev/sdc3 


-- 
 <daniel.iliev@gmail.com>


      reply	other threads:[~2009-08-10  7:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 18:24 raid10 problem with spare disk Daniel Iliev
2009-08-08 21:17 ` NeilBrown
2009-08-09  7:55   ` Daniel Iliev
2009-08-09 10:43     ` NeilBrown
2009-08-10  7:14       ` Daniel Iliev [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=20090810101457.0390d92a.daniel.iliev@gmail.com \
    --to=daniel.iliev@gmail.com \
    --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).