From: Neil Brown <neilb@suse.de>
To: Wakko Warner <wakko@animx.eu.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Device state during an incremental assembly
Date: Sun, 21 Nov 2010 17:19:48 +1100 [thread overview]
Message-ID: <20101121171948.4b793254@notabene.brown> (raw)
In-Reply-To: <20101120015225.GA9625@animx.eu.org>
On Fri, 19 Nov 2010 20:52:25 -0500
Wakko Warner <wakko@animx.eu.org> wrote:
> I am not on this list, please always CC me.
>
> Is there anyway to determine the array state after incrementally adding a
> device? I was hoping to find something in /sys but I was unable to. I was
> trying not to parse the output of mdadm for each invocation.
>
Yes.
Note: if you don't find that there is enough detail in this answer, it simply
reflects the level of detail in the question :-)
NeilBrown
next prev parent reply other threads:[~2010-11-21 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 1:52 Device state during an incremental assembly Wakko Warner
2010-11-21 6:19 ` Neil Brown [this message]
2010-11-21 14:41 ` Wakko Warner
2010-11-21 20:58 ` Neil Brown
2010-11-21 22:45 ` Wakko Warner
2010-11-21 23:19 ` Neil Brown
2010-11-22 1:39 ` Wakko Warner
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=20101121171948.4b793254@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=wakko@animx.eu.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).