From: Wols Lists <antlists@youngman.org.uk>
To: Roger Heflin <rogerheflin@gmail.com>,
Heinz Mauelshagen <heinzm@redhat.com>
Cc: Kyle Sanderson <kyle.leet@gmail.com>,
linux-raid@vger.kernel.org, Song Liu <song@kernel.org>,
device-mapper development <dm-devel@redhat.com>,
John Stoffel <john@stoffel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [dm-devel] RAID4 with no striping mode request
Date: Wed, 15 Feb 2023 14:53:04 +0000 [thread overview]
Message-ID: <0f5aafed-7b1a-99ac-57fc-c5de9a269b92@youngman.org.uk> (raw)
In-Reply-To: <CAAMCDee2hV1YP=119Rorz1uGTnyBD5q9hb20PvMq89FHow2wPw@mail.gmail.com>
On 15/02/2023 11:44, Roger Heflin wrote:
> WOL: current SSD's are rated for around 1000-2000 writes. So a 1Tb
> disk can sustain 1000-2000TB of total writes. And writes to
> filesystem blocks would get re-written more often than data blocks.
> How well it would work would depend on how often the data is deleted
> and re-written.
When did that guy do that study of SSDs? Basically hammered them to
death 24/7? I think it took about three years of continuous write/erase
cycles to destroy them.
Given that most drives are obsolete long before they've had three years
of writes ... the conclusion was that - for the same write load -
"modern" (as they were several years ago) SSDs would probably outlast
mechanical drives for the same workload.
(Cheap SD cards, on the other hand ...)
Cheers,
Wol
next prev parent reply other threads:[~2023-02-15 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 3:07 Kyle Sanderson
2023-02-13 19:40 ` John Stoffel
2023-02-13 21:11 ` Kyle Sanderson
2023-02-14 18:37 ` Song Liu
[not found] ` <CAM23Vxr8LkkcVDFfW1=qEYGgo7JG1qx62eWSV4WOw4_MnD+TZA@mail.gmail.com>
2023-02-14 22:28 ` [dm-devel] " Roger Heflin
2023-02-15 7:23 ` Kyle Sanderson
2023-02-15 9:40 ` Wols Lists
[not found] ` <CAM23VxpzY6qYsdTYxe01FT7AJvEbODf8X_vq8ALL35TfyrB8xQ@mail.gmail.com>
2023-02-15 11:44 ` Roger Heflin
2023-02-15 14:53 ` Wols Lists [this message]
2023-02-15 15:22 ` Roger Heflin
2023-02-16 0:01 ` Kyle Sanderson
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=0f5aafed-7b1a-99ac-57fc-c5de9a269b92@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=dm-devel@redhat.com \
--cc=heinzm@redhat.com \
--cc=john@stoffel.org \
--cc=kyle.leet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rogerheflin@gmail.com \
--cc=song@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
all inboxes | Powered by JetHome®