From: Neil Brown <neilb@suse.de>
To: Norman Elton <normelton@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: How many drives are bad?
Date: Thu, 21 Feb 2008 15:28:13 +1100 [thread overview]
Message-ID: <18364.64989.891076.596011@notabene.brown> (raw)
In-Reply-To: message from Norman Elton on Tuesday February 19
On Tuesday February 19, normelton@gmail.com wrote:
> So I had my first "failure" today, when I got a report that one drive
> (/dev/sdam) failed. I've attached the output of "mdadm --detail". It
> appears that two drives are listed as "removed", but the array is
> still functioning. What does this mean? How many drives actually
> failed?
The array is configured for 8 devices, but on 6 are active. So you
have lost data.
Of the two missing devices, one is still in the array and is marked as
fault. One is simply not present at all.
Hence "Failed Devices: 1". i.e. there is one failed device in the
array.
It looks like you have been running a degraded array for a while
(maybe not a long while) and the device has then failed.
"mdadm --monitor"
will send you mail if you have a degraded array.
NeilBrown
>
> This is all a test system, so I can dink around as much as necessary.
> Thanks for any advice!
>
> Norman Elton
>
> ====== OUTPUT OF MDADM =====
>
> Version : 00.90.03
> Creation Time : Fri Jan 18 13:17:33 2008
> Raid Level : raid5
> Array Size : 6837319552 (6520.58 GiB 7001.42 GB)
> Device Size : 976759936 (931.51 GiB 1000.20 GB)
> Raid Devices : 8
> Total Devices : 7
> Preferred Minor : 4
> Persistence : Superblock is persistent
>
> Update Time : Mon Feb 18 11:49:13 2008
> State : clean, degraded
> Active Devices : 6
> Working Devices : 6
> Failed Devices : 1
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> UUID : b16bdcaf:a20192fb:39c74cb8:e5e60b20
> Events : 0.110
>
> Number Major Minor RaidDevice State
> 0 66 1 0 active sync /dev/sdag1
> 1 66 17 1 active sync /dev/sdah1
> 2 66 33 2 active sync /dev/sdai1
> 3 66 49 3 active sync /dev/sdaj1
> 4 66 65 4 active sync /dev/sdak1
> 5 0 0 5 removed
> 6 0 0 6 removed
> 7 66 113 7 active sync /dev/sdan1
>
> 8 66 97 - faulty spare /dev/sdam1
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-02-21 4:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 17:23 How many drives are bad? Norman Elton
2008-02-19 17:31 ` Justin Piszcz
2008-02-19 18:24 ` Norman Elton
2008-02-19 18:33 ` Justin Piszcz
2008-02-19 18:38 ` Norman Elton
2008-02-19 19:13 ` Justin Piszcz
2008-02-19 19:25 ` Norman Elton
2008-02-19 19:44 ` Steve Fairbairn
2008-02-20 0:22 ` Guy Watkins
2008-02-20 7:21 ` Peter Grandi
2008-02-21 18:12 ` Norman Elton
2008-02-21 20:54 ` pg_mh, Peter Grandi
2008-02-21 21:45 ` Peter Rabbitson
2008-02-21 4:28 ` Neil Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-20 4:03 Guy Watkins
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=18364.64989.891076.596011@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=normelton@gmail.com \
/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).