From: Neil Brown <neilb@cse.unsw.edu.au>
To: Jeff Hill <jhill@hrpost.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm mail option configuration
Date: Thu, 30 May 2002 08:53:22 +1000 (EST) [thread overview]
Message-ID: <15605.23522.860348.236412@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Jeff Hill on Wednesday May 29
On Wednesday May 29, jhill@hrpost.com 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.
>
> Okay, changed. My choice was arbitrary, just assumed it would be
> reasonable -- I'm moving it on to a heavily loaded production server
> and the e-mail isn't constantly monitored so I assumed . . . .
You assumed what? Are you thinking that it wil send mail every $delay
seconds if there is a problem, and you didn't want to be spammed?
Mdadm only sends mail when it notices a drive fail, not when it
notices that a drive is failed.
i.e. if on one poll the drive is working, and on the next poll the
drive is not working, then it sends mail saying "The drive just
failed".
So when you were testing, was "mdadm -Fs" actually running at the
moment when you simulated a drive failure?
NeilBrown
next prev parent reply other threads:[~2002-05-29 22:53 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 [this message]
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
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.23522.860348.236412@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=jhill@hrpost.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).