All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Alex <mysqlstudent@gmail.com>,
	Linux RAID <linux-raid@vger.kernel.org>,
	Neil Brown <neilb@suse.de>
Subject: Re: Need to remove failed disk from RAID5 array
Date: Thu, 19 Jul 2012 10:25:25 -0400	[thread overview]
Message-ID: <500818D5.4080208@tmr.com> (raw)
In-Reply-To: <20120719091611.22e16100@natsu>

Roman Mamedov wrote:
> On Wed, 18 Jul 2012 22:44:06 -0400
> Alex <mysqlstudent@gmail.com> wrote:
>
>> I'm not sure what stats I could provide to troubleshoot this further.
>> At this rate, the 2.7T array will take a full day to resync. Is that
>> to be expected?
> 1) did you try increasing stripe_cache_size?
>
> 2) maybe it's an "Advanced Format" drive, the RAID partition is not properly
> aligned?
>
That's a good argument for not using "whole disk" array members, a partition can 
be started at a good offset and may perform better. As for the speed, since it 
is reconstructing the array data (hope the other drives are okay), every block 
written requires three blocks read and a reconstruct in cpu and memory. You can 
use "blockdev" to increase readahead, and set the devices to use the deadline 
scheduler, that _may_ improve things somewhat, but you have to read three block 
to write one, so it's not going to be fast.

-- 
Bill Davidsen <davidsen@tmr.com>
   We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination.  -me, 2010



  reply	other threads:[~2012-07-19 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 23:17 Need to remove failed disk from RAID5 array Alex
2012-07-18 20:26 ` Bill Davidsen
2012-07-19  2:44   ` Alex
2012-07-19  3:16     ` Roman Mamedov
2012-07-19 14:25       ` Bill Davidsen [this message]
2012-07-19 14:35         ` Roman Mamedov
2012-07-19 14:51           ` Bill Davidsen
2012-07-19 21:08         ` NeilBrown
2012-07-20  1:04           ` Alex
2012-07-20  1:22             ` Bill Davidsen
2012-07-20  1:37             ` NeilBrown
2012-07-23  4:14             ` Bill Davidsen
2012-07-24 14:02               ` Alex
2012-07-19 15:37       ` Alex

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=500818D5.4080208@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mysqlstudent@gmail.com \
    --cc=neilb@suse.de \
    --cc=rm@romanrm.ru \
    /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.