From: Brad Campbell <lists2009@fnarfbargle.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: linux-raid@vger.kernel.org
Subject: Re: What the heck happened to my array? (No apparent data loss).
Date: Mon, 04 Apr 2011 13:59:03 +0800 [thread overview]
Message-ID: <4D995E27.3060800@fnarfbargle.com> (raw)
In-Reply-To: <AANLkTi=2GNYdySbCDXmaDC8-8vF8GU9V3Uoy1qByNq58@mail.gmail.com>
On 03/04/11 23:47, Roberto Spadim wrote:
> what kernel version? more informations about your linux box?
The kernel version and architecture were the first 2 lines of the E-mail
you top posted over.
What would you like to know about the box? It's a 6 core Phenom-II with
16G of ram. 2 LSI SAS 9240 controllers configured with 10 x 1TB SATA
Drives in a RAID-6(md0) & 3 x 750GB SATA drives in a RAID-5(md2).
The boot drives are a pair of 1TB SATA drives in multiple RAID-1's using
the on-board AMD chipset controller and there is a 64GB SSD on a
separate PCI-E Marvell 7042m Controller.
The array in question is :
root@srv:~# mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sat Jan 8 11:25:17 2011
Raid Level : raid6
Array Size : 7814078464 (7452.09 GiB 8001.62 GB)
Used Dev Size : 976759808 (931.51 GiB 1000.20 GB)
Raid Devices : 10
Total Devices : 9
Persistence : Superblock is persistent
Update Time : Mon Apr 4 13:53:59 2011
State : clean, degraded, recovering
Active Devices : 9
Working Devices : 9
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Reshape Status : 29% complete
New Chunksize : 64K
Name : srv:server (local to host srv)
UUID : d00a11d7:fe0435af:07c8d4d6:e3b8e34e
Events : 429198
Number Major Minor RaidDevice State
0 8 32 0 active sync /dev/sdc
1 8 176 1 active sync /dev/sdl
2 8 192 2 active sync /dev/sdm
3 8 80 3 active sync /dev/sdf
4 8 16 4 active sync /dev/sdb
5 8 96 5 active sync /dev/sdg
6 0 0 6 removed
7 8 64 7 active sync /dev/sde
8 8 0 8 active sync /dev/sda
9 8 112 9 active sync /dev/sdh
root@srv:~#
Subsequent investigation has shown sdd has a pending reallocation and I
can only assume the unidentified IO error was as a result of tripping up
on that. It still does not explain why all IO to the array froze after
the drive was kicked.
next prev parent reply other threads:[~2011-04-04 5:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 13:32 What the heck happened to my array? (No apparent data loss) Brad Campbell
2011-04-03 15:47 ` Roberto Spadim
2011-04-04 5:59 ` Brad Campbell [this message]
2011-04-04 16:49 ` Roberto Spadim
2011-04-05 0:47 ` What the heck happened to my array? Brad Campbell
2011-04-05 6:10 ` NeilBrown
2011-04-05 9:02 ` Brad Campbell
2011-04-05 11:31 ` NeilBrown
2011-04-05 11:47 ` Brad Campbell
2011-04-08 1:19 ` Brad Campbell
2011-04-08 9:52 ` NeilBrown
2011-04-08 15:27 ` Roberto Spadim
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=4D995E27.3060800@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.