From: Andrew Dunn <andrew.g.dunn@gmail.com>
To: linux-raid list <linux-raid@vger.kernel.org>
Subject: RAID 6 Failure follow up
Date: Sun, 08 Nov 2009 09:07:37 -0500 [thread overview]
Message-ID: <4AF6D0A9.6000901@gmail.com> (raw)
This is kind of interesting:
storrgie@ALEXANDRIA:~$ sudo mdadm --assemble --force /dev/md0
mdadm: no devices found for /dev/md0
All of the devices are there in /dev, so I wanted to examine them:
storrgie@ALEXANDRIA:~$ sudo mdadm --examine /dev/sde1
/dev/sde1:
Magic : a92b4efc
Version : 00.90.00
UUID : 397e0b3f:34cbe4cc:613e2239:070da8c8 (local to host
ALEXANDRIA)
Creation Time : Fri Nov 6 07:06:34 2009
Raid Level : raid6
Used Dev Size : 976759808 (931.51 GiB 1000.20 GB)
Array Size : 6837318656 (6520.58 GiB 7001.41 GB)
Raid Devices : 9
Total Devices : 9
Preferred Minor : 0
Update Time : Sun Nov 8 08:57:04 2009
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 4
Spare Devices : 0
Checksum : 4ff41c5f - correct
Events : 43
Chunk Size : 1024K
Number Major Minor RaidDevice State
this 0 8 65 0 active sync /dev/sde1
0 0 8 65 0 active sync /dev/sde1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 113 3 active sync /dev/sdh1
4 4 0 0 4 faulty removed
5 5 0 0 5 faulty removed
6 6 0 0 6 faulty removed
7 7 0 0 7 faulty removed
8 8 8 193 8 active sync /dev/sdm1
First raid device shows the failures....
One of the 'removed' devices:
storrgie@ALEXANDRIA:~$ sudo mdadm --examine /dev/sdi1
/dev/sdi1:
Magic : a92b4efc
Version : 00.90.00
UUID : 397e0b3f:34cbe4cc:613e2239:070da8c8 (local to host
ALEXANDRIA)
Creation Time : Fri Nov 6 07:06:34 2009
Raid Level : raid6
Used Dev Size : 976759808 (931.51 GiB 1000.20 GB)
Array Size : 6837318656 (6520.58 GiB 7001.41 GB)
Raid Devices : 9
Total Devices : 9
Preferred Minor : 0
Update Time : Sun Nov 8 08:53:30 2009
State : active
Active Devices : 9
Working Devices : 9
Failed Devices : 0
Spare Devices : 0
Checksum : 4ff41b2f - correct
Events : 21
Chunk Size : 1024K
Number Major Minor RaidDevice State
this 4 8 129 4 active sync /dev/sdi1
0 0 8 65 0 active sync /dev/sde1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 113 3 active sync /dev/sdh1
4 4 8 129 4 active sync /dev/sdi1
5 5 8 145 5 active sync /dev/sdj1
6 6 8 161 6 active sync /dev/sdk1
7 7 8 177 7 active sync /dev/sdl1
8 8 8 193 8 active sync /dev/sdm1
--
Andrew Dunn
http://agdunn.net
next reply other threads:[~2009-11-08 14:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 14:07 Andrew Dunn [this message]
2009-11-08 14:23 ` RAID 6 Failure follow up Roger Heflin
2009-11-08 14:30 ` Andrew Dunn
2009-11-08 18:01 ` Richard Scobie
2009-11-08 18:22 ` Andrew Dunn
2009-11-08 18:34 ` Joe Landman
2009-11-08 22:09 ` Andrew Dunn
2009-11-08 22:59 ` Richard Scobie
2009-11-09 2:45 ` Ryan Wagoner
2009-11-09 2:57 ` Richard Scobie
2009-11-09 8:09 ` Gabor Gombas
2009-11-09 10:08 ` Andrew Dunn
2009-11-09 11:34 ` Gabor Gombas
2009-11-09 22:04 ` Andrew Dunn
2009-11-10 10:55 ` Andrew Dunn
2009-11-10 11:34 ` Vincent Schut
2009-11-11 12:34 ` Andrew Dunn
2009-11-11 12:46 ` Vincent Schut
2009-11-17 8:40 ` Vincent Schut
2009-11-10 12:45 ` Ryan Wagoner
2009-11-08 14:36 ` Andrew Dunn
2009-11-08 14:56 ` Roger Heflin
2009-11-08 17:08 ` Andrew Dunn
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=4AF6D0A9.6000901@gmail.com \
--to=andrew.g.dunn@gmail.com \
--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).