Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
	General discussion - ask "questions," receive answers and advice
	from other ZFS users  <zfs-discuss@list.zfsonlinux.org>,
	Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Fwd: [OT][X-POST] RAID-6 hw rebuild speed
Date: Tue, 1 Dec 2020 11:34:39 +0000	[thread overview]
Message-ID: <5FC62A4F.9000100@youngman.org.uk> (raw)
In-Reply-To: <CAJH6TXgED_UGRcLNVU+-1p8BVMapJkRmvZMndLYAKjX_j6f7iw@mail.gmail.com>

On 01/12/20 09:57, Gandalf Corvotempesta wrote:
> Sorry for the OT and X-POST but these 2 lists are full of skilled
> storage engineer.
> For a very,very,very,very long time I used 15k SAS 3.5'' disks. A
> RAID-6 hardware (8 disks) took about 20 hours to rebuild.
> 
> Now I've replaced a 3.5 disks with a 15k SAS 2.5'' disk. raid is
> rebuilding properly, but the ETA is less then 1 hours.
> 
> I've moved from a 20 hours rebuild to about 50 minutes rebuild, by
> just changing one 3.5' disks with a 2.5'
> 
> Is this normal ? I'm thinking something strange is happening
> 
Your rebuild time is effectively the time it takes to write to the new
disk. So I'm guessing if you had to wipe and rebuild one of the old
disks it would again be 20 hours. So what's different about the new disk?

Yes I know it's a 2.5". But could it be it's SATA-3 as opposed to the
old ones being SATA-2? There's a whole bunch of things it could be.

But my money's on it having a bigger cache. The ETA is based on how fast
it can read from the existing array and the rebuild hasn't yet filled
the cache. Once that fills up and the disk write speed kicks in, the ETA
will start climbing fast as the write speed starts dominating the ETA.
That said, it'll probably be faster than the old 20hrs, but I don't know
by how much.

Cheers,
Wol

  parent reply	other threads:[~2020-12-01 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJH6TXjsg+OE5rUpK+RqeFJRxBiZJ94ToOdUD5ajjwXzYft9Vw@mail.gmail.com>
2020-12-01  9:57 ` Fwd: [OT][X-POST] RAID-6 hw rebuild speed Gandalf Corvotempesta
     [not found]   ` <CAJ1=CigDVO9-2uSBw8Fbv-86y8G6XOFM2CjRs1yURAczgB6ydA@mail.gmail.com>
2020-12-01 11:28     ` [zfs-discuss] " Gandalf Corvotempesta
2020-12-01 11:34   ` Wols Lists [this message]
2020-12-01 13:01     ` Roger Heflin
2020-12-01 17:15       ` Gandalf Corvotempesta
2020-12-02  1:21         ` Roger Heflin
2021-02-26 14:04     ` [zfs-discuss] " rob_mailing_lists&rbabb net

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=5FC62A4F.9000100@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=zfs-discuss@list.zfsonlinux.org \
    /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