From: "NeilBrown" <neilb@suse.de>
To: Patrick Ringl <patrick.ringl@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: 2.6.29 - raid10 issue - spares do not get synched automatically
Date: Sun, 29 Mar 2009 07:46:04 +1100 (EST) [thread overview]
Message-ID: <b5623e48a92119937c6527b7f9564ed4.squirrel@neil.brown.name> (raw)
In-Reply-To: <49CE19F0.5040809@gmx.de>
On Sat, March 28, 2009 11:37 pm, Patrick Ringl wrote:
> Hello,
>
> I am using 2.6.29 on a debian lenny. Anyway, I am having problems with a
> raid10 sandbox setup consisting of 4 loopback devices. To make a long
> story short:
>
> I created a raid10 array with all these 4 devices (loop0-loop3)
> then I set two devices faulty, removed them .. checked if I can still
> write to the array (which I could, so I/O errors, nothing in dmesg):
>
> BUT - here it comes: once I am trying to (re)add them (I zero'ed the
> superblock before) they're only getting added as spares and the array
> will not sync.
>
> Here's the logfile with mdadm -D /dev/md0 in between so one can see what
> is going on:
>
> http://pa#ste.debian.net/31758/
>
Linux RAID10 with
Raid Level : raid10
Raid Devices : 4
Layout : near=2, far=1
Will layout data like this:
disk0 disk1 disk2 disk3
A A B B
C C D D
E E F F
You have removed disk0 and disk1, so A,C,E don't exist
any more. You should get IO errors when you try to access
that data.
There is nothing that can be recovered, so the drives remain
as spares.
NeilBrown
next prev parent reply other threads:[~2009-03-28 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 12:37 2.6.29 - raid10 issue - spares do not get synched automatically Patrick Ringl
2009-03-28 20:46 ` NeilBrown [this message]
2009-03-28 22:21 ` Patrick Ringl
2009-03-28 22:44 ` NeilBrown
2009-03-28 22:41 ` Patrick Ringl
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=b5623e48a92119937c6527b7f9564ed4.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=patrick.ringl@gmx.de \
/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).