From: Phil Karn <karn@ka9q.net>
To: Alberto Bursi <bobafetthotmail@gmail.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
Steven Fosdick <stevenfosdick@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Rich Rauenzahn <rrauenza@gmail.com>
Subject: Re: Western Digital Red's SMR and btrfs?
Date: Mon, 11 May 2020 15:42:44 -0700 [thread overview]
Message-ID: <9bbad15c-1bd1-e91a-ae50-bb1e643c19e2@ka9q.net> (raw)
In-Reply-To: <69847faf-5fb3-9eac-b819-373a0f814044@gmail.com>
On 5/11/20 14:13, Alberto Bursi wrote:
>
> Afaik drive-managed SMR drives (i.e. all drives that disguise
> themselves as non-SMR) are acting like a SSD, writing in empty "zones"
> first and then running garbage collection later to consolidate the
> data. TRIM is used for the same reasons SSDs also use it.
> This is the way they are working around the performance penalty of
> SMR, as it's the same limitation NAND flash also has (you can write
> only a full cell at a time).
>
> See here for example
> https://support-en.wd.com/app/answers/detail/a_id/25185
>
> -Alberto
Right, I understand that (some?) SMR drives support TRIM for the same
reason that SSDs do (well, a very similar reason). My question was
whether there'd be any reason for a NON-SMR drive to support TRIM, or if
TRIM support necessarily implies shingled recording. I didn't know
shingled recording was in any general purpose 2.5" spinning laptop
drives like mine, and there's no mention of SMR in the HGST manual.
Phil
next prev parent reply other threads:[~2020-05-11 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 5:24 Western Digital Red's SMR and btrfs? Rich Rauenzahn
2020-05-04 23:08 ` Zygo Blaxell
2020-05-04 23:24 ` Chris Murphy
2020-05-05 2:00 ` Zygo Blaxell
2020-05-05 2:22 ` Chris Murphy
2020-05-05 3:26 ` Zygo Blaxell
2020-05-09 21:00 ` Phil Karn
2020-05-09 21:46 ` Steven Fosdick
2020-05-11 5:06 ` Zygo Blaxell
2020-05-11 20:35 ` Phil Karn
2020-05-11 21:13 ` Alberto Bursi
2020-05-11 22:42 ` Phil Karn [this message]
2020-05-12 0:12 ` Zygo Blaxell
2020-05-12 2:17 ` Alberto Bursi
2020-05-11 4:06 ` Damien Le Moal
2020-05-05 9:30 ` Dan van der Ster
-- strict thread matches above, loose matches on Subject: below --
2020-05-02 12:26 Torstein Eide
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=9bbad15c-1bd1-e91a-ae50-bb1e643c19e2@ka9q.net \
--to=karn@ka9q.net \
--cc=bobafetthotmail@gmail.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rrauenza@gmail.com \
--cc=stevenfosdick@gmail.com \
/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