linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: earny@net4u.de
Cc: Neil Brown <neilb@suse.de>, Mike <mikee@mikee.ath.cx>,
	linux-raid@vger.kernel.org
Subject: Re: FailSpare event?
Date: Sat, 13 Jan 2007 23:34:26 +0000	[thread overview]
Message-ID: <87odp2pkl9.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <873b6ere4s.fsf@hades.wkstn.nix> (nix@esperi.org.uk's message of "13 Jan 2007 18:25:19 -0000")

On 13 Jan 2007, nix@esperi.org.uk spake thusly:

> On 12 Jan 2007, Ernst Herzberg told this:
>> Then every about 60 sec 4 times
>>
>> event=SpareActive
>> mddev=/dev/md3
>
> I see exactly this on both my RAID-5 arrays, neither of which have any
> spare device --- nor have any active devices transitioned to spare
> (which is what that event is actually supposed to mean).

Hm, the manual says that it means that a spare has transitioned to
active (which seems more likely). Perhaps the comment at line 82 of
Monitor.c is wrong, or I just don't understand what a `reverse
transition' is supposed to be.

-- 
`He accused the FSF of being "something of a hypocrit", which
 shows that he neither understands hypocrisy nor can spell.'
   --- jimmybgood

  reply	other threads:[~2007-01-13 23:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 22:11 FailSpare event? Mike
2007-01-11 22:23 ` Neil Brown
2007-01-11 22:36   ` Mike
2007-01-11 22:59     ` Neil Brown
2007-01-11 23:06       ` Mike
2007-01-12  0:05         ` Mike Hardy
2007-01-12  0:40         ` Corey Hickey
2007-01-12  0:48         ` Martin Schröder
2007-01-12 14:34   ` Ernst Herzberg
2007-01-13 18:10     ` Nix
2007-01-13 23:34       ` Nix [this message]
2007-01-13 23:38       ` Nix
     [not found]         ` <45ABA3E4.3050800@tmr.com>
2007-01-15 19:59           ` Nix
2007-01-14 15:01       ` Nix
2007-01-14 21:20         ` Neil Brown
2007-01-15 20:08           ` Nix
2007-01-13 22:29   ` Mike

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=87odp2pkl9.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=earny@net4u.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=mikee@mikee.ath.cx \
    --cc=neilb@suse.de \
    /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).