linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anu Matthew <anu.matthew@bms.com>
To: linux-raid@vger.kernel.org
Subject: monitoring multipath arrays plus inconsistent /proc/mdstat?
Date: Thu, 21 Oct 2004 12:16:17 -0400	[thread overview]
Message-ID: <4177E0D1.7090001@bms.com> (raw)

Hello,

mdadm --monitor or mdadm --follow does not report anything if a link to 
my multipath array fails, which makes sense at times. (?)

On rhel 2.1 at least, sometimes I have seen that /proc/mdstat is not 
consistent as in this case, it has marked /dev/sdi as failed, where as 
mdadm -D on md3 has reported both links to be active, and in fact is 
using the "failed link" in mdstat as the active path..!!

------------------from /proc/mdstat---------------------------------------
md3 : active multipath sdd[1] sdi[0](F)

----------------from mdadm o/p--------------------------
[root@tlr root]# mdadm -D /dev/md3
/dev/md3:
<snip>
<snip>
    Number   Major   Minor   RaidDevice State
       0       8      128        0      active sync   /dev/sdi

       1       8       48        1      spare   /dev/sdd

----------------------------------------------------------------------------

Whom to trust here? How do we monitor multipath arrays effectively?

--Matt

             reply	other threads:[~2004-10-21 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 16:16 Anu Matthew [this message]
2004-10-21 16:51 ` monitoring multipath arrays plus inconsistent /proc/mdstat? Lars Marowsky-Bree
2004-10-22  5:41   ` Lajber Zoltan
2004-10-22  9:17     ` Lars Marowsky-Bree
2004-10-22 20:44       ` Anu Matthew
2004-10-22 21:25         ` Lars Marowsky-Bree

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=4177E0D1.7090001@bms.com \
    --to=anu.matthew@bms.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).