From: Mike <mikee@mikee.ath.cx>
To: linux-raid@vger.kernel.org
Subject: FailSpare event?
Date: Thu, 11 Jan 2007 22:11:52 +0000 (UTC) [thread overview]
Message-ID: <eo6cn8$5se$1@sea.gmane.org> (raw)
Can someone tell me what this means please? I just received this in
an email from one of my servers:
From: mdadm monitoring [root@$DOMAIN.com]
To: root@$DOMAIN.com
Subject: FailSpare event on /dev/md2:$HOST.$DOMAIN.com
This is an automatically generated mail message from mdadm
running on $HOST.$DOMAIN.com
A FailSpare event had been detected on md device /dev/md2.
It could be related to component device /dev/sde2.
Faithfully yours, etc.
On this machine I execute:
$ cat /proc/mdstat
Personalities : [raid5] [raid4] [raid1]
md0 : active raid1 sdf1[2](S) sde1[3](S) sdd1[4](S) sdc1[5](S) sdb1[1] sda1[0]
104320 blocks [2/2] [UU]
md1 : active raid1 sdf3[2](S) sde3[3](S) sdd3[4](S) sdc3[5](S) sdb3[1] sda3[0]
3068288 blocks [2/2] [UU]
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]
unused devices: <none>
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
# fdisk -l /dev/sde
[root@elo ~]# fdisk -l /dev/sde
Disk /dev/sde: 146.8 GB, 146815733760 bytes
255 heads, 63 sectors/track, 17849 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 * 1 13 104391 fd Linux raid autodetect
/dev/sde2 14 17465 140183190 fd Linux raid autodetect
/dev/sde3 17466 17847 3068415 fd Linux raid autodetect
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?
Mike
next reply other threads:[~2007-01-11 22:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 22:11 Mike [this message]
2007-01-11 22:23 ` FailSpare event? 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
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='eo6cn8$5se$1@sea.gmane.org' \
--to=mikee@mikee.ath.cx \
--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).