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 09:44:58 +1100 (EST) [thread overview]
Message-ID: <cf9bf069bb0926d0a5a79879af44e7fd.squirrel@neil.brown.name> (raw)
In-Reply-To: <49CEA2FC.8020505@gmx.de>
On Sun, March 29, 2009 9:21 am, Patrick Ringl wrote:
> Hello Neil,
>
> NeilBrown wrote:
>> 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.
>>
> Sorry, but I removed loop0 and loop2 so that would be disk0 and disk2 -
> so ACE as well as BDF should still exist and recover. Could you explain
> this, I am I just getting you wrong?
From the Pastezone thing...
-----------------------------------------------------
Number Major Minor RaidDevice State
0 7 2 0 active sync /dev/loop2
1 7 0 1 active sync /dev/loop0
2 7 1 2 active sync /dev/loop1
3 7 3 3 active sync /dev/loop3
pari:/mnt/debian# mdadm --manage /dev/md0 -f /dev/loop2
mdadm: set /dev/loop2 faulty in /dev/md0
pari:/mnt/debian# mdadm --manage /dev/md0 -f /dev/loop0
mdadm: set /dev/loop0 faulty in /dev/md0
---------------------------------------------------
So while you did remove loop0 and loop2, these were disk1 and disk0.
NeilBrown
next prev parent reply other threads:[~2009-03-28 22:44 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
2009-03-28 22:21 ` Patrick Ringl
2009-03-28 22:44 ` NeilBrown [this message]
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=cf9bf069bb0926d0a5a79879af44e7fd.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).