All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Rauenzahn <rrauenza@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Western Digital Red's SMR and btrfs?
Date: Fri, 1 May 2020 22:24:57 -0700	[thread overview]
Message-ID: <CAG+QAKXuaah3tkhQLd7mD3bx+pc3JZdXkUg6yr0R8=Zv2vXnhw@mail.gmail.com> (raw)

Has there been any btrfs discussion off the list (I haven't seen any
SMR/shingled mails in the archive since 2016 or so) regarding the news
that WD's Red drives are actually SMR?

I'm using these reds in my btrfs setup (which is 2-3 drives in RAID1
configuration, not parity based RAIDs.)   I had noticed that adding a
new drive took a long time, but other than than, I haven't had any
issues that I know of.  They've lasted quite a long time, although I
think my NAS would be considered more of a cold storage/archival.
Photos and Videos.

Is btrfs raid1 going to be the sweet spot on these drives?

If I start swapping these out -- is there a recommended low power
drive?  I'd buy the red pro's, but they spin faster and produce more
heat and noise.

Rich

             reply	other threads:[~2020-05-02  5:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02  5:24 Rich Rauenzahn [this message]
2020-05-04 23:08 ` Western Digital Red's SMR and btrfs? 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
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
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='CAG+QAKXuaah3tkhQLd7mD3bx+pc3JZdXkUg6yr0R8=Zv2vXnhw@mail.gmail.com' \
    --to=rrauenza@gmail.com \
    --cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.