All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Bowes <robin-lists@robinbowes.com>
To: Steven Ihde <x-linux-raid@hamachi.dyndns.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Thanks :)
Date: Sat, 23 Oct 2004 08:52:53 +0100	[thread overview]
Message-ID: <417A0DD5.4030109@robinbowes.com> (raw)
In-Reply-To: <20041022205144.GA28719@hamachi.dyndns.org>

Steven Ihde wrote:
> On Fri, 22 Oct 2004 21:17:16 +0100, Robin Bowes wrote:
> 
>>David Greaves wrote:
>>
>>>I got this yesterday
>>>
>>>#################
>>>This is an automatically generated mail message from mdadm
>>>running on cu.dgreaves.com
>>>
>>>A Fail event had been detected on md device /dev/md0.
>>>#################
>>
>>David,
>>
>>How have you set things up to achieve this?
> 
> 
> See the section on Monitor mode (-F option) in the mdadm man page.
> Debian's mdadm package, for example, sets it up so mdadm -F gets run
> automatically at boot time to monitor your arrays.


Sorry, I wasn't clear enough in my question...

I am aware of mdadms' monitor mode; in fact, I'm sure it used to run 
when I first started using mdadm (on Fedora Core 2 installed from rpm 
built myself from src rpm).

I seem to remember that this was disabled at some stage but can't 
remember the detail - possibly something to do with preventing the array 
from shutting down cleanly because mdadm -F was open on it.

I am hoping that someone can suggest how best to run mdadm -F on Fedora 
Core 2. Perhaps it could be as simple as creating a script in 
/etc/init.d/ which would terminate before the array is shutdown?

R.
-- 
http://robinbowes.com

  reply	other threads:[~2004-10-23  7:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-22 18:06 Thanks :) David Greaves
2004-10-22 20:17 ` Robin Bowes
2004-10-22 20:51   ` Steven Ihde
2004-10-23  7:52     ` Robin Bowes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-29 14:45 Thanks! KeithG
2023-11-29 16:59 ` Thanks! Grant Erickson
2023-12-01  6:35   ` Thanks! Marcus Folkesson
2018-11-07 17:46 thanks! tungolcild
2007-12-27 10:13 Thanks! Jan Evert van Grootheest
2006-08-26 23:08 Thanks! Robert Brockway
2005-04-08 17:47 Thanks!! Dustin Lang
2005-04-08 19:10 ` Thanks!! Colin Leroy
2005-04-08 21:21   ` Thanks!! Dan Malek
2005-04-09  2:21     ` Thanks!! Daniele Lacamera
2005-04-09  7:50     ` Thanks!! Colin Leroy
2004-03-20 14:15 Thanks :) neilb
2002-06-09 17:24 Thanks!!! Philipp Vollmer

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=417A0DD5.4030109@robinbowes.com \
    --to=robin-lists@robinbowes.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=x-linux-raid@hamachi.dyndns.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 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.