From: Phil Turmel <philip@turmel.org>
To: Michael Munger <michael@highpoweredhelp.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: [UU_] Won't go away
Date: Tue, 27 Oct 2015 08:34:10 -0400 [thread overview]
Message-ID: <562F6F42.4070302@turmel.org> (raw)
In-Reply-To: <562F6DEA.3010409@highpoweredhelp.com>
Hi Michael,
{Added the list back and fixed the top-posting. Convention on
kernel.org is to reply-to-all, trim replies, and bottom post or interleave.}
On 10/27/2015 08:28 AM, Michael Munger wrote:
> On 10/27/2015 08:23 AM, Phil Turmel wrote:
>> On 10/27/2015 08:17 AM, Michael Munger wrote:
>>> Personalities : [raid6] [raid5] [raid4]
>>> md0 : active raid5 sdd1[3] sdc1[1] sdb1[0]
>>> 3906764800 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2]
>>> [UU_]
>>> [>....................] recovery = 0.1% (2611780/1953382400)
>>> finish=1737.7min speed=18709K/sec
>>> bitmap: 0/15 pages [0KB], 65536KB chunk
>> What's to fix? Did you try waiting for the recovery to finish?
>> Creating an array generally isn't instant -- the redundancy has to be
>> computed over the entire array.
>>
>> Now, you might have speed limits that are making it slower than possible
>> (see man md), but multiple hours on big devices is perfectly normal.
> I thought [UU_] indicated a physical drive problem, not logical array
> issue. I'll wait until 2pm when this is supposed to finish and re-check.
I mentioned the speed limits because 20MB/sec is kinda low for modern
drives. You can probably speed that up.
> It will be GREAT if that's all it was... my being impatient!
>
> PS... lsdrv is a great utility. thanks for making it available on Github.
You're welcome :-)
Phil
next prev parent reply other threads:[~2015-10-27 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 12:17 [UU_] Won't go away Michael Munger
2015-10-27 12:23 ` Phil Turmel
[not found] ` <562F6DEA.3010409@highpoweredhelp.com>
2015-10-27 12:34 ` Phil Turmel [this message]
2015-10-27 12:24 ` Robin Hill
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=562F6F42.4070302@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=michael@highpoweredhelp.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 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.