From: Mike Snitzer <msnitzer@lnxi.com>
To: linux-hotplug@vger.kernel.org
Subject: Hotplug support in Linux software raid?
Date: Mon, 05 Jan 2004 18:00:24 +0000 [thread overview]
Message-ID: <20040105110024.C18367@lnxi.com> (raw)
I have a need to be notified when the kernel changes the state of storage
that is managed by Linux MD. Is using hotplug in linux's md a reasonable
way to achieve asynchronous notification of raid state changes?
An example use would be when an available spare disk of a md array is made
live by the kernel after a failed disk in the array is marked faulty. So
maybe 2 events are triggered: 1) spare disk<foo> is now live 2) failed
disk<bar> is now marked faulty. This causes the kernel to issue hotplug
events to the userspace /sbin/hotplug which in turn triggers a
configurable action to be taken in userspace.
Ultimately I could use mdadm's monitor functionality to recieve
notification but this is _not_ ideal in that it polls on a specified
interval.
I'd appreciate any insight/suggestions.
Thanks.
--
Mike Snitzer msnitzer@lnxi.com
Linux Networx http://www.lnxi.com
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-01-05 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 18:00 Mike Snitzer [this message]
2004-01-05 22:47 ` Hotplug support in Linux software raid? Greg KH
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=20040105110024.C18367@lnxi.com \
--to=msnitzer@lnxi.com \
--cc=linux-hotplug@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).