From: Patrick Ringl <patrick.ringl@gmx.de>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: 2.6.29 - raid10 issue - spares do not get synched automatically
Date: Sat, 28 Mar 2009 13:37:04 +0100 [thread overview]
Message-ID: <49CE19F0.5040809@gmx.de> (raw)
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://paste.debian.net/31758/
Any ideas?
PS: Please CC to me since I am not subscribed.
regards,
Patrick
next reply other threads:[~2009-03-28 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 12:37 Patrick Ringl [this message]
2009-03-28 20:46 ` 2.6.29 - raid10 issue - spares do not get synched automatically NeilBrown
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=49CE19F0.5040809@gmx.de \
--to=patrick.ringl@gmx.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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).