From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: GFS2: Add LED support to GFS2
Date: Wed, 22 Jul 2009 16:02:31 +0100 [thread overview]
Message-ID: <1248274951.3298.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20090722145534.GA6035@basil.fritz.box>
Hi,
On Wed, 2009-07-22 at 16:55 +0200, Andi Kleen wrote:
> > It would be difficult to make that generic since the errors and the
> > resulting actions which can be taken vary from fs to fs. The main reason
> > that I didn't do it at this point in time is that the GFS2 error
> > handling needs revising anyway, and once that is done (probably with an
> > errors= option similar to ext2/3/4) it might be possible to think about
> > LED support for that,
>
> I was thinking to have a couple of generic functions like:
>
> log_activity()
> error_happened()
>
> ...
>
> that everyone could call.
>
> -Andi
>
>
Indeed, but we'd need to allow for different classes of activity or
errors, and then filtering them per-LED. With my proposed patch that is
avoided due to having a small number of triggers on the different
events, so selecting the trigger acts as a filter on the event type.
So I guess what I'm really getting at, is what would the user interface
be for this scheme to set up the LEDs?
I did consider adding a feature to filter events on a per superblock
basis, but I decided against it in the end, as it seemed to be making
things too complicated (how should we specify the superblock? what
should the user interface be?).
Maybe there is an easy way to do that which I've not spotted...
Steve.
next prev parent reply other threads:[~2009-07-22 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 10:56 [Cluster-devel] GFS2: Add LED support to GFS2 Steven Whitehouse
[not found] ` <87k5203hdx.fsf@basil.nowhere.org>
2009-07-22 14:51 ` [Cluster-devel] " Steven Whitehouse
[not found] ` <20090722145534.GA6035@basil.fritz.box>
2009-07-22 15:02 ` Steven Whitehouse [this message]
[not found] ` <20090722151521.GB6035@basil.fritz.box>
2009-07-22 15:24 ` Steven Whitehouse
2009-07-29 15:08 ` Pavel Machek
2009-07-29 15:52 ` Steven Whitehouse
2009-07-31 11:53 ` Pavel Machek
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=1248274951.3298.11.camel@localhost.localdomain \
--to=swhiteho@redhat.com \
/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).