From: Neil Brown <neilb@cse.unsw.edu.au>
To: Danilo Godec <danci@agenda.si>
Cc: Jeff Hill <jhill@hronline.com>, linux-raid@vger.kernel.org
Subject: Re: mdadm mail option configuration
Date: Thu, 30 May 2002 09:10:41 +1000 (EST) [thread overview]
Message-ID: <15605.24561.501893.319158@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Danilo Godec on Wednesday May 29
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.
>
> Now I'm not sure whether mdadm is supposed to send mail on every check? Or
> is it sending mail just when a BAD thing happens?
Exactly.
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.
>
> D.
>
> PS: The PROGRAM was started more often (I think three times).
That's quite possible.
Once for Fail
Once for RebuildStarted
maybe some RebuildNN
Once for SpareActive
NeilBrown
next prev parent reply other threads:[~2002-05-29 23:10 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 [this message]
2002-05-30 6:25 ` Danilo Godec
2002-05-31 14:09 ` Jakob Østergaard
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=15605.24561.501893.319158@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=danci@agenda.si \
--cc=jhill@hronline.com \
--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 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).