linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Ross Vandegrift <ross@jose.lug.udel.edu>
Cc: James Neale <james@promotionstudios.com>, linux-raid@vger.kernel.org
Subject: Re: RAID5 problem
Date: Thu, 08 Dec 2005 09:20:40 +0000	[thread overview]
Message-ID: <4397FAE8.6030009@dgreaves.com> (raw)
In-Reply-To: <20051208014950.GA23381@jose.lug.udel.edu>

Ross Vandegrift wrote:

>On Thu, Dec 08, 2005 at 11:07:36AM +1100, James Neale wrote:
>  
>
>>Hi Ross
>>I'm a bit of a mdadm newb and have been wrangling with -monitor rather 
>>unsucccessfully.
>>Currently  I'm manually checking /proc/mdstat until I've sorted out 
>>something better.
>>I'm running a single 1TB raid5 on 6 disks (one is spare) which has been 
>>smooth so far.
>>Any pointers or examples for that reliable noisy mailing beeping script 
>>of yours in /etc/bashrc
>>    
>>
>
>The blob is below, just stick it in your bashrc.  My idea was that
>everytime I spawn a shell (which is a lot!), mdstat gets checked.
>
>What issues are you having with --monitor?  It should be pretty
>automatic if you let it scan.  I just run something like this:
>
>/sbin/mdadm -F -s -f -y
>
>This stats mdadm in --monitor mode, scans for devices, daemonizes, and
>records its results in syslog.
>
>Here's what runs in my bashrc:
>
># Scream and cry a lot if the RAID looks weird!
>if /bin/grep _ /proc/mdstat; then
>        for ((scream = 0; scream < 5; scream ++)); do
>                echo -e "POSSIBLE PROBLEM WITH RAID"
>                sleep 0.1
>        done
>        cat /proc/mdstat
>fi
>
>  
>
Have a look at monit
And festival

Quite a cool combination....


David




-- 


  reply	other threads:[~2005-12-08  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04 14:21 RAID5 problem Alfons Andorfer
2005-12-04 21:47 ` Neil Brown
2005-12-05  1:44   ` Ross Vandegrift
2005-12-05  2:44     ` Neil Brown
2005-12-06  2:26       ` Ross Vandegrift
     [not found]     ` <43977948.6050507@promotionstudios.com>
2005-12-08  1:49       ` Ross Vandegrift
2005-12-08  9:20         ` David Greaves [this message]
2005-12-05 10:59   ` Alfons Andorfer
  -- strict thread matches above, loose matches on Subject: below --
2005-12-04 21:28 Andrew Burgess
2005-12-04 21:49 ` Neil Brown

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=4397FAE8.6030009@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=james@promotionstudios.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=ross@jose.lug.udel.edu \
    /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).