From: "Jakob Østergaard" <jakob@unthought.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Danilo Godec <danci@agenda.si>, Jeff Hill <jhill@hronline.com>,
linux-raid@vger.kernel.org
Subject: Re: mdadm mail option configuration
Date: Fri, 31 May 2002 16:09:37 +0200 [thread overview]
Message-ID: <20020531160937.A22230@unthought.net> (raw)
In-Reply-To: <15605.24561.501893.319158@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Thu, May 30, 2002 at 09:10:41AM +1000
On Thu, May 30, 2002 at 09:10:41AM +1000, Neil Brown wrote:
> On Wednesday May 29, danci@agenda.si wrote:
> > On Wed, 29 May 2002, Neil Brown wrote:
> >
> > > > Then, I just have an init script that runs:
> > > >
> > > > /sbin/mdadm -Fs --delay=600 &
> > >
> > > Why 600 (10 minutes)?? I would suggest 60seconds for normal operation
> > > and 1 second for testing.
> >
> > I've tried this and maybe I'm missing something. I've set a 5 second
> > interval for checking and I only got one mail - notifiyng me about
> > a failure.
>
> Yes, that's right. One failure, one email. I'm not in the business
> of spam.
What we do with SysOrb (blatant plug: http://sysorb.com) is to send out an
e-mail immediately when the RAID degrades, and then a new mail every N seconds.
The RAID may be checked every 10 seconds, and the user may configure N to be,
say, 1800 seconds. So the failure is detected almost immediately, while the
alert will only be sent every half hour for example.
We've found that this repetition is useful as a reminder. It also motivates
people to either fix the problem, or schedule downtime for the check saying
that it will be down for another 24 hours for example.
Once you are administering more than a few machines, one alert can get lost in
the occational heap.
...
> It has occurred to me that it could be useful to send mail at startup
> if there appear to be any abnormalities, but I think I would prefer
> that sort of functionality to be external. A sysdamin might want that
> mail are reboot, or every night, or every week, or never. A simple:
> grep -s > /dev/nu $magic_pattern /proc/mdstat &&
> mail -s "Raid problem on `hostname`" root << END
> Possible RAID problem, please check.
> `hostname`
> `cat /proc/mdstat
> END
>
> is all that is needed.
In general, I think that these small scripts are really nice and all, if that
is "good enough" for you. Once they are no longer good enough, start looking
into real monitoring systems.
NetSaint could be hacked into supporting RAID I'm sure. And if you want to
save the hackery and can accept a commercial solution, well, then I plugged one
just above ;)
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
-
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
next prev parent reply other threads:[~2002-05-31 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <message from Jeff Hill on Wednesday May 29>
[not found] ` <message from Jeff Hill on Tuesday May 28>
2002-05-28 16:04 ` mdadm mail option configuration Jeff Hill
2002-05-29 10:46 ` Neil Brown
2002-05-29 12:29 ` Jeff Hill
2002-05-29 22:53 ` Neil Brown
2002-05-30 14:11 ` Jeff Hill
2002-05-29 14:04 ` Danilo Godec
2002-05-29 23:10 ` Neil Brown
2002-05-30 6:25 ` Danilo Godec
2002-05-31 14:09 ` Jakob Østergaard [this message]
2002-06-01 1:43 Haofeng Kou
2002-06-01 11:56 ` Jakob Østergaard
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=20020531160937.A22230@unthought.net \
--to=jakob@unthought.net \
--cc=danci@agenda.si \
--cc=jhill@hronline.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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.