All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Testing /proc/mdstat parsing
Date: Fri, 20 Sep 2013 18:03:21 -0500	[thread overview]
Message-ID: <l1ik7i$epk$1@ger.gmane.org> (raw)

For my NAS monitoring daemon, I have decided to check the status of my
RAID arrays by parsing /proc/mdstat.  (I did consider using sysfs,
ioctls, or mdadm, but /proc/mdstat seems to be the most efficient way
to get a "snapshot" of the state of all the arrays.)

I've played around with various setups and failure scenarios in a VM,
and I've also reviewed md_seq_show() in md.c.  Based on this, I've
written parsing code that can handle everything that I've been able to
come up with so far.  But that's just me ...

Does anyone know of or have a collection of /proc/mdstat examples that
can be used for testing?

Thanks!

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
========================================================================


                 reply	other threads:[~2013-09-20 23:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='l1ik7i$epk$1@ger.gmane.org' \
    --to=arequipeno@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.