From: Lars Marowsky-Bree <lmb@suse.de>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Monitoring filesystems / blockdevice for errors
Date: Sun, 17 Dec 2000 19:43:35 +0100 [thread overview]
Message-ID: <20001217194334.V5323@marowsky-bree.de> (raw)
In-Reply-To: <20001217153453.O5323@marowsky-bree.de> <Pine.LNX.4.10.10012171314050.16143-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10012171314050.16143-100000@coffee.psychology.mcmaster.ca>; from "Mark Hahn" on 2000-12-17T13:23:52
On 2000-12-17T13:23:52,
Mark Hahn <hahn@coffee.psychology.mcmaster.ca> said:
> > Short of parsing syslog messages, which isn't particularly great.
> what's wrong with it?
Because it means having to know about all potential messages the filesystems
might dump out.
> reinventing /proc/kmsg and klogd would be tre gross.
Well, only one process can read kmsg and get notified about new messages at
any time, so that makes the monitoring depend on klogd/syslogd working, which
given a write error by syslog might not be the case...
> > I don't have a real idea how this could be added, short of adding a field to
> > /proc/partitions (error count) or something similiar.
> for reporting errors, that might be OK, but it's not a particularly nice
> _notification_ mechanism...
Well, yes.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Perfection is our goal, excellence will be tolerated. -- J. Yahl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-17 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 14:34 Monitoring filesystems / blockdevice for errors Lars Marowsky-Bree
2000-12-17 18:23 ` Mark Hahn
2000-12-17 18:43 ` Lars Marowsky-Bree [this message]
2000-12-18 5:28 ` Peter Samuelson
2000-12-18 8:46 ` Jan-Benedict Glaw
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=20001217194334.V5323@marowsky-bree.de \
--to=lmb@suse.de \
--cc=hahn@coffee.psychology.mcmaster.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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