From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Seagate hard drives with dual actuators.
Date: Fri, 15 Nov 2024 17:13:27 -0500 [thread overview]
Message-ID: <CAGfcS_mvwurzi9tZMa=_JHhDtOkzZDWUtX8mXyg4TdoWn-ZTRw@mail.gmail.com> (raw)
In-Reply-To: <115451235.nniJfEyVGO@rogueboard>
On Fri, Nov 15, 2024 at 10:35 AM Michael <confabulate@kintzios.com> wrote:
>
> Host managed SMRs (HM-SMR) require the OS and FS to be aware of the need for
> sequential writes and manage submitted data sympathetically to this limitation
> of the SMR drive, by queuing up random writes in batches and submitting these
> as a sequential stream.
>
> I understand the ext4-lazy option and some patches on btrfs have improved
> performance of these filesystems on SMR drivers, but perhaps f2fs will perform
> better? :-/
IMO a host-managed solution is likely to be the only thing that will
work reliably. If the drive supports discard/trim MAYBE a dumber
drive might be able to be used with the right filesystem. Even if
you're doing "write-once" workloads any kind of metadata change is
going to cause random writes unless the filesystem was designed for
SMR. Ideally you'd store metadata on a non-SMR device, though it
isn't strictly necessary with a log-based approach.
If the SMR drive tries really hard to not look like an SMR drive and
doesn't support discard/trim then even an SMR-aware solution probably
won't be able to use it effectively. The drive is going to keep doing
read-before-write cycles to preserve data even if there is nothing
useful to preserve.
--
Rich
next prev parent reply other threads:[~2024-11-15 22:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 23:10 [gentoo-user] Seagate hard drives with dual actuators Dale
2024-11-14 0:46 ` Matt Jolly
2024-11-14 13:05 ` Dale
2024-11-14 7:55 ` Wols Lists
2024-11-14 16:48 ` Dale
2024-11-15 0:18 ` [OT] " Peter Humphrey
2024-11-15 8:41 ` [gentoo-user] Hollerith (was: Seagate hard drives with dual actuators) karl
2024-11-15 9:51 ` [OT] Re: [gentoo-user] Seagate hard drives with dual actuators Wols Lists
2024-11-14 11:21 ` Michael
2024-11-14 17:00 ` Dale
2024-11-14 19:12 ` Michael
2024-11-14 19:51 ` Frank Steinmetzger
2024-11-14 19:55 ` Frank Steinmetzger
2024-11-14 23:14 ` Peter Humphrey
2024-11-14 20:33 ` Dale
2024-11-14 20:57 ` Rich Freeman
2024-11-14 23:10 ` Dale
2024-11-15 0:59 ` Rich Freeman
2024-11-15 5:53 ` Dale
2024-11-15 10:09 ` Michael
2024-11-15 11:59 ` Dale
2024-11-15 15:35 ` Michael
2024-11-15 16:36 ` Dale
2024-11-15 22:13 ` Rich Freeman [this message]
2024-11-16 11:02 ` Michael
2024-11-16 14:36 ` Rich Freeman
2024-11-16 19:47 ` Michael
2024-11-16 20:13 ` Rich Freeman
2024-11-16 23:21 ` Wol
2024-11-17 11:22 ` Michael
2024-11-17 21:26 ` Rich Freeman
2024-11-17 23:04 ` Jack
2024-11-18 0:23 ` Rich Freeman
2024-11-18 2:32 ` Matt Jolly
2024-11-15 10:38 ` Frank Steinmetzger
2024-11-15 12:19 ` Dale
2024-11-14 22:38 ` Wols Lists
2024-11-15 9:35 ` Michael
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='CAGfcS_mvwurzi9tZMa=_JHhDtOkzZDWUtX8mXyg4TdoWn-ZTRw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.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