From: Roger Heflin <rogerheflin@gmail.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: Wols Lists <antlists@youngman.org.uk>,
"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 19:21:41 -0600 [thread overview]
Message-ID: <CAAMCDefZDakjB4JTF4twzXssBKz3tm29jJJao9zS1+nQOYAnPg@mail.gmail.com> (raw)
In-Reply-To: <CAJH6TXjLCuG41-YSkibAMHumoEOXApEQbxFqc47YicTyp3uzTQ@mail.gmail.com>
122 to 204 MB/sec old if efficient writing all would take about an hour.
200 to 300 MB/sec new. if efficient writing all 600gb woudl take 2400sec.
so it should be maybe 2x faster.
So to get 20 hours, I am going to guess the old disk had the write
cache turned off and the disk working badly, that would explain it
being that much slower.
It may mean all of the old disk has the write cache on the disk
disabled and the new one does not have it disabled, or the hardware
raid is more efficiently working with the write cache off with the new
disk vs the old disk. Or it could be the write cache is the same and
the new disk with new firmware works better with command queuing so
wastes less time seeking back and forth.
On Tue, Dec 1, 2020 at 11:15 AM Gandalf Corvotempesta
<gandalf.corvotempesta@gmail.com> wrote:
>
> Il giorno mar 1 dic 2020 alle ore 14:01 Roger Heflin
> <rogerheflin@gmail.com> ha scritto:
> > So what is the model of each disk and how big is the partition used
> > for the array on each of the 8 disks?
>
> Old disk: Seagate ST3600057SS 3.5''
> New disk: Seagate ST600MP0006 2.5''
>
> One huge virtual disk, 3271G
next prev parent reply other threads:[~2020-12-02 1:22 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 [this message]
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=CAAMCDefZDakjB4JTF4twzXssBKz3tm29jJJao9zS1+nQOYAnPg@mail.gmail.com \
--to=rogerheflin@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).