From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 0 of 2] Introduction
Date: Fri, 03 Sep 2004 12:27:31 +1000 [thread overview]
Message-ID: <20040903122034.15346.patches@notabene> (raw)
Two patches for md in 2.6.9-rc1-mm2
The first adds support for notifying user-space of events in md.
The mechanism is very simple. A reader of /proc/mdstat can select for
"exceptional" events. When select/poll indicates one of these, the
reader should re-read /proc/mdstat from the top looking for changes, and then
select again.
If the reader opens for write as well (O_RDWR) (only root can do
this), then it indicates that it is prepared to take remedial action.
This is currently only relevant for multipath. On last-drive-failure,
if there is a reader of /proc/mdstat that has an open for write, then
multipath will wait for that reader to add a new drive or take other
action before resubmitting the failed requests.
The second patch just fixes a counter in raid5/6 which could get out-by-one, and so
produce confusing messages.
(I think I sent a single item of junk just before this, sorry about that. Please
ignore it).
NeilBrown
next reply other threads:[~2004-09-03 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 2:27 NeilBrown [this message]
2004-09-03 2:27 ` [PATCH md 1 of 2] Add interface to md driver for userspace monitoring of events NeilBrown
2004-09-03 10:19 ` Andrew Morton
2004-09-06 1:05 ` Neil Brown
2004-09-06 14:02 ` Christoph Hellwig
2004-09-06 22:53 ` Neil Brown
2004-09-06 23:07 ` Andrew Morton
2004-09-07 0:53 ` Neil Brown
2004-09-07 10:45 ` Christoph Hellwig
2004-09-03 2:27 ` [PATCH md 2 of 2] Correct "working_disk" counts for raid5 and raid6 NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 4:45 [PATCH md 0 of 2] Introduction NeilBrown
2004-12-01 0:49 NeilBrown
2005-02-09 22:22 NeilBrown
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=20040903122034.15346.patches@notabene \
--to=neilb@cse.unsw.edu.au \
--cc=akpm@osdl.org \
--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.