From: Stan Hoeppner <stan@hardwarefreak.com>
To: Ross Boylan <ross@biostat.ucsf.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: How do I tell which disk failed?
Date: Mon, 07 Jan 2013 23:19:25 -0600 [thread overview]
Message-ID: <50EBAC5D.8080000@hardwarefreak.com> (raw)
In-Reply-To: <1357610701.16366.13.camel@corn.betterworld.us>
On 1/7/2013 8:05 PM, Ross Boylan wrote:
> I see my array is reconstructing, but I can't tell which disk failed.
> md0 : active raid1 sda1[0] sdc2[2] sdb2[1]
> 96256 blocks [3/3] [UUU]
>
> md1 : active raid1 sda3[0] sdc4[2] sdb4[1]
> 730523648 blocks [3/3] [UUU]
Your two md/RAID1 arrays are built on partitions on the same set of 3
disks. You likely didn't have a disk failure, or md0 would be
rebuilding as well. Your failure, or hiccup, is of some other nature,
and apparently only affected md1.
> [>....................] resync = 0.4% (3382400/730523648) finish=14164.9min speed=855K/sec
Rebuilding a RAID1 on modern hardware should scream. You're getting
resync throughput of less than 1MB/s. Estimated completion time is 9.8
_days_ to rebuild a mirror partition. This is insanely high.
Either you've tweaked your resync throughput down to 1MB/s, or you have
some other process(es) doing serious IO, robbing the resync of
throughput. Consider running iotop to determine if another process(es)
is eating IO bandwidth.
--
Stan
next prev parent reply other threads:[~2013-01-08 5:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 2:05 How do I tell which disk failed? Ross Boylan
2013-01-08 5:19 ` Stan Hoeppner [this message]
2013-01-08 6:59 ` Ross Boylan
2013-01-08 7:17 ` Chris Murphy
2013-01-08 7:49 ` Ross Boylan
2013-01-08 8:48 ` Chris Murphy
2013-01-08 9:32 ` Ross Boylan
2013-01-08 17:36 ` Chris Murphy
2013-01-08 22:30 ` Stan Hoeppner
2013-01-08 7:59 ` Ross Boylan
2013-01-08 9:10 ` Chris Murphy
2013-01-08 21:54 ` Ross Boylan
2013-01-08 22:38 ` Chris Murphy
2013-01-08 23:13 ` Ross Boylan
2013-01-09 0:43 ` Chris Murphy
2013-01-08 23:03 ` Stan Hoeppner
2013-01-08 5:55 ` Chris Murphy
2013-01-08 9:55 ` Mikael Abrahamsson
2013-01-08 17:20 ` Ross Boylan
2013-01-08 21:24 ` pg_mh, Peter Grandi
2013-01-08 22:34 ` Stan Hoeppner
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=50EBAC5D.8080000@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=ross@biostat.ucsf.edu \
/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.