From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Replacing drives with larger ones in a 4 drive raid1
Date: Thu, 9 Jun 2016 15:20:47 +0000 (UTC) [thread overview]
Message-ID: <pan$6ab4$792ded48$cf23daab$a8e4c2@cox.net> (raw)
In-Reply-To: 022F65B5-228D-4EEF-95C9-3C269B63B290@bueechi.net
boli posted on Wed, 08 Jun 2016 20:55:13 +0200 as excerpted:
> Recently I had the idea to replace the 6 TB HDDs with 8 TB ones ("WD
> Red"), because their price is now acceptable.
Are those the 8 TB SMR "archive" drives?
I haven't been following the issue very closely, but be aware that there
were serious issues with those drives a few kernels back, and that while
those issues are now fixed, the drives themselves operate rather
differently than normal drives, and simply don't work well in normal
usage.
The short version is that they really are designed for archiving and work
well when used for that purpose -- a mostly write once and leave it there
for archiving and retrieval but rarely if ever rewrite it, type usage.
However, they work rather poorly in normal usage where data is rewritten,
because they have to rewrite entire zones of data, and that takes much
longer than simply rewriting individual sectors on normal drives does.
With the kernel patches to fix the initial problems they do work well
enough, tho performance may not be what you expect, but the key to
keeping them working well is being aware that they continue to do
rewrites in the background for long after they are done with the initial
write, and shutting them down while they are doing them can be an issue.
Due to btrfs' data checksumming feature, small variances to data that
wouldn't normally be detected on non-checksumming filesystems were
detected far sooner on btrfs, making it far more sensitive to these small
errors. However, if you use the drives for their intended nearly write-
only purpose, and/or very seldom power down the drives at all or do so
only long after (give it half an hour, say) any writes have completed, as
long as you're running a current kernel with the initial issues patched,
you should be fine. Just don't treat them like normal drives.
If OTOH you need more normal drive usage including lots of data rewrites,
especially if you frequently poweroff the devices, strongly consider
avoiding those 8 TB SMR drives, at least until the technology has a few
more years to mature.
There's more information on other threads on the list and on other lists,
if you need it and nobody posts more direct information (such as the
specific patches in question and what specific kernel versions they hit)
here. I could find it but I'd have to do a search in my own list
archives, and now that you are aware of the problem, you can of course do
the search as well, if you need to. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-06-09 15:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 18:55 Replacing drives with larger ones in a 4 drive raid1 boli
2016-06-09 15:20 ` Duncan [this message]
2016-06-09 17:30 ` bOli
2016-06-10 18:56 ` Jukka Larja
2016-06-11 13:13 ` boli
2016-06-12 10:35 ` boli
2016-06-12 15:24 ` Henk Slager
2016-06-12 17:03 ` boli
2016-06-12 19:03 ` Henk Slager
2016-06-13 3:54 ` Duncan
2016-06-13 12:24 ` Austin S. Hemmelgarn
2016-06-14 19:28 ` boli
2016-06-15 3:19 ` Duncan
2016-06-16 0:09 ` boli
2016-06-16 18:18 ` boli
2016-06-17 6:25 ` Duncan
2016-06-19 17:38 ` boli
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='pan$6ab4$792ded48$cf23daab$a8e4c2@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 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).