From: Neil Brown <neilb@suse.de>
To: Mike <mikee@mikee.ath.cx>
Cc: linux-raid@vger.kernel.org
Subject: Re: FailSpare event?
Date: Fri, 12 Jan 2007 09:23:41 +1100 [thread overview]
Message-ID: <17830.47341.560158.521091@notabene.brown> (raw)
In-Reply-To: message from Mike on Thursday January 11
On Thursday January 11, mikee@mikee.ath.cx wrote:
> Can someone tell me what this means please? I just received this in
> an email from one of my servers:
>
....
>
> A FailSpare event had been detected on md device /dev/md2.
>
> It could be related to component device /dev/sde2.
It means that mdadm has just noticed that /dev/sde2 is a spare and is faulty.
You would normally expect this if the array is rebuilding a spare and
a write to the spare fails however...
>
> md2 : active raid5 sdf2[4] sde2[5](F) sdd2[3] sdc2[2] sdb2[1] sda2[0]
> 560732160 blocks level 5, 256k chunk, algorithm 2 [5/5] [UUUUU]
That isn't the case here - your array doesn't need rebuilding.
Possible a superblock-update failed. Possibly mdadm only just started
monitoring the array and the spare has been faulty for some time.
>
> Does the email message mean drive sde2[5] has failed? I know the sde2 refers
> to the second partition of /dev/sde. Here is the partition table
It means that md thinks sde2 cannot be trusted. To find out why you
would need to look at kernel logs for IO errors.
>
> I have partition 2 of drive sde as one of the raid devices for md. Does the (S)
> on sde3[2](S) mean the device is a spare for md1 and the same for md0?
>
Yes, (S) means the device is spare. You don't have (S) next to sde2
on md2 because (F) (failed) overrides (S).
You can tell by the position [5], that it isn't part of the array
(being a 5 disk array, the active positions are 0,1,2,3,4).
NeilBrown
next prev parent reply other threads:[~2007-01-11 22:23 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 [this message]
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
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=17830.47341.560158.521091@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mikee@mikee.ath.cx \
/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).