All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hervé Eychenne" <rv@eychenne.org>
To: Molle Bestefich <molle.bestefich@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Questions about software RAID
Date: Wed, 20 Apr 2005 11:32:22 +0200	[thread overview]
Message-ID: <20050420093222.GL3103@eychenne.org> (raw)
In-Reply-To: <62b0912f05042002266bfef91d@mail.gmail.com>

On Wed, Apr 20, 2005 at 11:26:28AM +0200, Molle Bestefich wrote:

> David Greaves wrote:
> > Guy wrote:
> > > Well, I agree with KISS, but from the operator's point of view!
> > >
> > > I want...
> > [snip]
> > 
> > Fair enough.
> [snip]
> > should the LED control code be built into mdadm?

> Obviously not.
> But currently, a LED control app would have to pull information from
> /proc/mdstat, right?
> mdstat is a crappy place to derive any state from.
> It currently seems to have a dual purpose:
>  - being a simple textual representation of RAID state for the user.
>  - providing MD state information for userspace apps.

> That's not good.

I could not agree more.

> There seems to be an obvious lack of a properly thought out interface
> to notify userspace applications of MD events (disk failed --> go
> light a LED, etc).

> Please correct me if I'm on the wrong track, in which case the rest of
> this posting will be bogus.  Maybe there are IOCTLs or such that I'm
> not aware of.

> I'm not sure how a proper interface could be done (so I'm basically
> just blabbering).  ACPI has some sort of event system, but the MD one
> would need to be more flexible.  For instance userspace apps has to
> pick up on MD events such as disk failures, even if the userspace app
> happens to not be running in the exact moment that the event occurs
> (due to system restart, daemon restart or what not).  So the system
> that ACPI uses is probably unsuited.

> Perhaps a simple logfile would do.

No, as it requires active polling.
I think something like a netlink device would be more accurate, but I'm
not a kernel guru.

 Herve

-- 
 _
(°=  Hervé Eychenne
//)  Homepage:          http://www.eychenne.org/
v_/_ WallFire project:  http://www.wallfire.org/

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2005-04-20  9:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 11:00 Questions about software RAID bernd
2005-04-19 14:40 ` Hervé Eychenne
2005-04-19 15:27   ` David Greaves
2005-04-19 15:54     ` Hervé Eychenne
2005-04-19 16:53       ` Frank Wittig
2005-04-19 17:54         ` Hervé Eychenne
2005-04-19 19:46           ` Frank Wittig
2005-04-20  4:15             ` Guy
2005-04-20  4:47               ` Questions about software RAID - red led Alvin Oga
2005-04-20  7:59               ` Questions about software RAID David Greaves
2005-04-20  9:26                 ` Molle Bestefich
2005-04-20  9:32                   ` Hervé Eychenne [this message]
2005-04-20 17:36                     ` Molle Bestefich
2005-04-20 11:16                   ` Peter T. Breuer
2005-04-20 12:34                     ` Lars Marowsky-Bree
2005-04-20 15:49               ` Martin K. Petersen
2005-04-21  1:21                 ` Guy
  -- strict thread matches above, loose matches on Subject: below --
2005-04-18 19:50 tmp
2005-04-18 20:12 ` David Greaves
2005-04-18 23:12   ` tmp
2005-04-19  6:36     ` Peter T. Breuer
2005-04-19  7:15     ` Luca Berra
2005-04-19  8:08       ` David Greaves
2005-04-19 12:18         ` Michael Tokarev
2005-04-18 20:15 ` Peter T. Breuer
2005-04-18 20:50 ` Frank Wittig

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=20050420093222.GL3103@eychenne.org \
    --to=rv@eychenne.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=molle.bestefich@gmail.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 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.