linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>,
	linux-raid@vger.kernel.org
Subject: Re: Growing RAID5 SSD Array
Date: Thu, 13 Mar 2014 06:58:04 -0500	[thread overview]
Message-ID: <53219D4C.2020207@hardwarefreak.com> (raw)
In-Reply-To: <53211C9D.8050607@websitemanagers.com.au>

On 3/12/2014 9:49 PM, Adam Goryachev wrote:
...
>     Number   Major   Minor   RaidDevice State
>        7       8       33        0      active sync   /dev/sdc1
>        6       8        1        1      active sync   /dev/sda1
>        8       8       49        2      active sync   /dev/sdd1
>        5       8       81        3      active sync   /dev/sdf1
>        9       8       65        4      active sync   /dev/sde1
...
> /dev/sda	Total_LBAs_Written	845235
> /dev/sdc	Total_LBAs_Written      851335
> /dev/sdd	Total_LBAs_Written      804564
> /dev/sde	Total_LBAs_Written	719767
> /dev/sdf	Total_LBAs_Written      719982
...
> So the drive with the highest writes 851335 and the drive with the
> lowest writes 719982 show a big difference. Perhaps I have a problem
> with the setup/config of my array, or similar?

This is normal for striped arrays.  If we reorder your write statistics
table to reflect array device order, we can clearly see the effect of
partial stripe writes.  These are new file allocations, appends, etc
that are smaller than stripe width.  Totally normal.  To get these close
to equal you'd need a chunk size of 16K or smaller.

> /dev/sdc	Total_LBAs_Written      851335
> /dev/sda	Total_LBAs_Written	845235
> /dev/sdd	Total_LBAs_Written      804564
> /dev/sde	Total_LBAs_Written	719767
> /dev/sdf	Total_LBAs_Written      719982

> So, I could simply do the following:
> mdadm --manage /dev/md1 --add /dev/sdb1
> mdadm --grow /dev/md1 --raid-devices=6
> 
> Probably also need to remove the bitmap and re-add the bitmap.

Might want to do

~$ echo 250000 > /proc/sys/dev/raid/speed_limit_min
~$ echo 500000 > /proc/sys/dev/raid/speed_limit_min

That'll bump min resync to 250 MB/s per drive, max 500 MB/s.  IIRC the
defaults are 1 MB/s and 100 MB/s.

> Can anyone suggest if what I am seeing is "normal", and should I just go
> ahead and add the extra disk?

Don't see why not.  You might want to stop drbd first.

-- 
Stan


  reply	other threads:[~2014-03-13 11:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13  2:49 Growing RAID5 SSD Array Adam Goryachev
2014-03-13 11:58 ` Stan Hoeppner [this message]
2014-03-17  5:43   ` Adam Goryachev
2014-03-17 21:43     ` Stan Hoeppner
2014-03-18  1:41       ` Adam Goryachev
2014-03-18 11:22         ` Stan Hoeppner
2014-03-18 23:25           ` Adam Goryachev
2014-03-19 20:45             ` Stan Hoeppner
2014-03-20  2:54               ` Adam Goryachev
2014-03-22 19:39                 ` Stan Hoeppner
2014-03-25 13:10                   ` Adam Goryachev
2014-03-25 20:31                     ` Stan Hoeppner
2014-04-05 19:25                       ` Adam Goryachev
2014-04-08 15:27                         ` Stan Hoeppner
2014-04-09  3:57                           ` Adam Goryachev
2014-04-10  8:06                             ` 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=53219D4C.2020207@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mailinglists@websitemanagers.com.au \
    /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).