From: Simon <simon.xhz@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: spare not becoming active
Date: Thu, 28 Jun 2007 12:06:09 -0400 [thread overview]
Message-ID: <4683DC71.3050200@gmail.com> (raw)
In-Reply-To: <4682C9ED.9040503@gmail.com>
> Number Major Minor RaidDevice State
> 0 0 0 0 removed
> 1 8 34 1 active sync /dev/sdc2
> 2 0 0 2 removed
>
> 3 8 82 - spare /dev/sdf2
> 4 8 66 - spare /dev/sde2
> 5 8 50 - faulty spare
> 6 8 18 - faulty spare
I was trying a couple things, but never got to change this status.
At one point I stopped the array and restarted it, and it didn't work. (I did it
before, so i don't see why...)
# /sbin/mdadm -R /dev/md0
mdadm: failed to run array /dev/md0: Invalid argument
I'm starting to think the documentation i read was very outdated, or only
touched the subject in surface, can you guys recommend a good reading, like a
companion to the man page?
Thanks,
Simon
next prev parent reply other threads:[~2007-06-28 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 20:34 spare not becoming active Simon
2007-06-28 16:06 ` Simon [this message]
2007-07-03 20:53 ` Simon
2007-07-03 22:20 ` Nix
2007-07-03 22:52 ` Simon
2007-07-03 22:54 ` Simon
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=4683DC71.3050200@gmail.com \
--to=simon.xhz@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).