From: "rob_mailing_lists&rbabb net" <Ufficio.Qualita@vvinternational.eu>
To: "Linux RAID Mailing List" <linux-raid@vger.kernel.org>
Subject: Re: [zfs-discuss] Fwd: [OT][X-POST] RAID-6 hw rebuild speed
Date: Fri, 26 Feb 2021 15:04:09 +0100 [thread overview]
Message-ID: <C23EDB1A0E6DB7CEEDF5FD24FF7C9BD44811F208@unknown> (raw)
In-Reply-To: <5FC62A4F.9000100@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]
Greetings! As you required, I have found to you several necessary
documents and attached them to this email. If you will want to find
additional information, you know, who can provide it.
On 2020-12-01 12:34, Linux RAID Mailing List wrote:
> 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
> ------------------------------------------ zfsonlinux: Discuss Permalink:
> https://zfsonlinux.topicbox.com/groups/zfs-discuss/T0168d10d08f31ca4-M1e0c7cc3b7c276450f1bdf1a
> Delivery options:
> https://zfsonlinux.topicbox.com/groups/zfs-discuss/subscription
[-- Attachment #2: prepared (68).zip --]
[-- Type: application/zip, Size: 15203 bytes --]
prev parent reply other threads:[~2021-02-26 14:11 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
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 ` rob_mailing_lists&rbabb net [this message]
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=C23EDB1A0E6DB7CEEDF5FD24FF7C9BD44811F208@unknown \
--to=ufficio.qualita@vvinternational.eu \
--cc=linux-raid@vger.kernel.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