From: Doug Ledford <dledford@redhat.com>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: mismatch_cnt again
Date: Sat, 07 Nov 2009 17:57:57 -0500 [thread overview]
Message-ID: <4AF5FB75.6030904@redhat.com> (raw)
In-Reply-To: <4AF5F3E1.4060509@eyal.emu.id.au>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On 11/07/2009 05:25 PM, Eyal Lebedinsky wrote:
> Doug,
>
> I can only see the cron job start a check:
> echo "check" > /sys/block/$dev/md/sync_action
> It does not wait for completion and does not report the count. Neither is
> the count reported to the system log.
>
> I replaced it with a script that does report.
Or you can updated to a later mdadm package. The one in rawhide has a
fairly well fletched out script now.
> Eyal
>
> Doug Ledford wrote:
>> On 11/07/2009 11:23 AM, Piergiorgio Sartor wrote:
>>> Side note: in F11 there is this cron.weekly raid-check, but
>>> nothing is reported (per email to root) in case of mismatch.
>>> Is there any plan to add a such a facility?
>>
>> Unless you've modified the default cron behaviour, then yes something is
>> reported to the user on a mismatch. The fact that the script goes from
>> being silent to echoing a warning will result in the cron job itself
>> emailing root the output of the script.
>
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-11-07 22:57 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 0:41 mismatch_cnt again Eyal Lebedinsky
2009-11-07 1:53 ` berk walker
2009-11-07 7:49 ` Eyal Lebedinsky
2009-11-07 8:08 ` Michael Evans
2009-11-07 8:42 ` Eyal Lebedinsky
2009-11-07 13:51 ` Goswin von Brederlow
2009-11-07 14:58 ` Doug Ledford
2009-11-07 16:23 ` Piergiorgio Sartor
2009-11-07 16:37 ` Doug Ledford
2009-11-07 22:25 ` Eyal Lebedinsky
2009-11-07 22:57 ` Doug Ledford [this message]
2009-11-08 15:32 ` Goswin von Brederlow
2009-11-09 18:08 ` Bill Davidsen
2009-11-07 22:19 ` Eyal Lebedinsky
2009-11-07 22:58 ` Doug Ledford
2009-11-08 15:46 ` Goswin von Brederlow
2009-11-08 16:04 ` Piergiorgio Sartor
2009-11-09 18:22 ` Bill Davidsen
2009-11-09 21:50 ` NeilBrown
2009-11-10 18:05 ` Bill Davidsen
2009-11-10 22:17 ` Peter Rabbitson
2009-11-13 2:15 ` Neil Brown
2009-11-09 19:13 ` Goswin von Brederlow
2009-11-08 22:51 ` Peter Rabbitson
2009-11-09 18:56 ` Piergiorgio Sartor
2009-11-09 21:14 ` NeilBrown
2009-11-09 21:54 ` Piergiorgio Sartor
2009-11-10 0:17 ` NeilBrown
2009-11-10 9:09 ` Peter Rabbitson
2009-11-10 14:03 ` Martin K. Petersen
2009-11-12 22:40 ` Bill Davidsen
2009-11-13 17:12 ` Martin K. Petersen
2009-11-14 17:01 ` Bill Davidsen
2009-11-17 5:19 ` Martin K. Petersen
2009-11-14 19:04 ` Goswin von Brederlow
2009-11-17 5:22 ` Martin K. Petersen
2009-11-10 19:52 ` Piergiorgio Sartor
2009-11-13 2:37 ` Neil Brown
2009-11-13 5:30 ` Goswin von Brederlow
2009-11-13 9:33 ` Peter Rabbitson
2009-11-15 21:05 ` Piergiorgio Sartor
2009-11-15 22:29 ` Guy Watkins
2009-11-16 1:23 ` Goswin von Brederlow
2009-11-16 1:37 ` Neil Brown
2009-11-16 5:21 ` Goswin von Brederlow
2009-11-16 5:35 ` Neil Brown
2009-11-16 7:40 ` Goswin von Brederlow
2009-11-12 22:57 ` Bill Davidsen
2009-11-09 18:11 ` Bill Davidsen
2009-11-09 20:58 ` Doug Ledford
2009-11-09 22:03 ` Eyal Lebedinsky
-- strict thread matches above, loose matches on Subject: below --
2009-11-12 19:20 greg
2009-11-13 2:28 ` Neil Brown
2009-11-13 5:19 ` Goswin von Brederlow
2009-11-15 1:54 ` Bill Davidsen
2009-11-16 21:36 greg
2009-11-16 22:14 ` Neil Brown
2009-11-17 4:50 ` Goswin von Brederlow
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=4AF5FB75.6030904@redhat.com \
--to=dledford@redhat.com \
--cc=eyal@eyal.emu.id.au \
--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).