From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Hendrik Friedel <hendrik@friedels.name>,
Tomasz Kusmierz <tom.kusmierz@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>, dave@jikos.cz
Subject: Re: Status of SMR with BTRFS
Date: Mon, 18 Jul 2016 14:44:49 -0400 [thread overview]
Message-ID: <667a14be-4a01-02f6-79f9-a8cd585f360d@gmail.com> (raw)
In-Reply-To: <bd311710-35c8-ce52-5b5a-96876330bde6@friedels.name>
On 2016-07-18 14:31, Hendrik Friedel wrote:
> Hello and thanks for your replies,
>
>>>>> It's a Seagate Expansion Desktop 5TB (USB3). It is probably a
>>>>> ST5000DM000.
>>>>
>>>> this is TGMR not SMR disk:
>> TGMR is a derivative of giant magneto-resistance, and is what's been
>> used in hard disk drives for decades now. With limited exceptions in
>> recent years and in ancient embedded systems, all modern hard drives are
>> TGMR based.
>
> Ok, thanks; So, TGMR does not say whether or not the Device is SMR or
> not, right?
I'm not 100% certain about that. Technically, the only non-firmware
difference is in the read head and the tracking. If it were me, I'd be
listing SMR instead of TGMR on the data sheet, but I'd be more than
willing to bet that many drive manufacturers won't think like that.
> While the Data-Sheet does not mention SMR and the 'Desktop' in the name
> rather than 'Archive' would indicate no SMR, some reviews indicate SMR
> (http://www.legitreviews.com/seagate-barracuda-st5000dm000-5tb-desktop-hard-drive-review_161241)
I know for a fact that at least through 2015, all 'Desktop' branded 3.5
inch Seagate hard drives up through 4TB in capacity used TGMR with 1TB
platters (500GB per side of the platter). I've got one of their 5TB
external drives at work (with 'Expansion' branding) which uses a 3.5
inch disk which based on testing I've done appears to be traditional
TGMR with either thinner platters (and thus more of them) or some other
method of improving areal storage density. Beyond that, I'm not sure,
but I believe that their 'Desktop' branding still means it's TGMR and
not SMR.
>
>
>>> In any case: the drive behaves like a SMR drive: I ran a benchmark on it
>>> with up to 200MB/s.
>>> When copying a file onto the drive in parallel the rate in the benchmark
>>> dropped to 7MB/s, while that particular file was copied at 40MB/s.
>> This type of performance degradation is actually not unexpected
>
> Ok. I was not aware. I expected some, but less impact.
There are a number of factors that contribute to this, I see less
degradation on enterprise disks than regular retail units, but it's
still there. Even with the insane precision they already have using
voice-coils for actuation of the head, there's a functional upper limit
on how fast it can move without risking damaging anything.
>
>
>> There's two things that should be clarified here:
> [...]
> Thanks for clarifying.
>
>>> Well, I'm no pro. But I found this:
>>> https://github.com/kdave/drafts/blob/master/btrfs/smr-mode.txt
>>> And this does sound like improvements to BTRFS can be done for SMR in a
>>> generic, not vendor/device specific manner.
>>>
>>> And I am wondering:
> [...]
>>> b) whether these improvements have been made already
>> Not yet.
>
> Ok, thanks.
> So I conclude that on SMR Drives, BTRFS has all benefits that it has on
> all other devices and there are no BTRFS related disadvantages in
> relation with BTRFS. Nevertheless, some improvements to BTRFS can be
> made in order to improve BTRFS with these drives.
I've come to pretty much the same conclusion in my usage. That said,
quite a few improvements could be made to BTRFS in general, not just
with respect to SMR drives.
I'd very much suggest avoiding USB connected SMR drives though, USB is
already poorly designed for storage devices (even with USB attached
SCSI), and most of the filesystem issues I see personally (not just with
BTRFS, but any other filesystem as well) are on USB connected storage,
so I'd be very wary of adding all the potential issues with SMR drives
on top of that as well.
next prev parent reply other threads:[~2016-07-18 18:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 18:29 Status of SMR with BTRFS Hendrik Friedel
2016-07-15 22:15 ` Tomasz Kusmierz
2016-07-16 10:29 ` Hendrik Friedel
2016-07-17 3:09 ` Tomasz Kusmierz
2016-07-17 9:08 ` Hendrik Friedel
2016-07-17 20:48 ` Henk Slager
2016-07-18 11:22 ` Austin S. Hemmelgarn
2016-07-18 18:31 ` Hendrik Friedel
2016-07-18 18:44 ` Austin S. Hemmelgarn [this message]
2016-07-18 19:05 ` Hendrik Friedel
2016-07-18 19:30 ` Austin S. Hemmelgarn
2016-07-18 22:29 ` Tomasz Kusmierz
2016-07-20 19:58 ` Chris Murphy
2016-07-21 12:46 ` Austin S. Hemmelgarn
2016-07-21 13:34 ` Chris Murphy
2016-07-21 14:02 ` Andrei Borzenkov
2016-07-21 14:12 ` Austin S. Hemmelgarn
2016-07-21 14:31 ` Chris Murphy
2016-07-21 15:35 ` Patrik Lundquist
-- strict thread matches above, loose matches on Subject: below --
2016-07-17 8:26 Matthias Prager
2016-07-17 20:10 ` Henk Slager
2016-07-17 21:44 ` Matthias Prager
2016-07-18 18:49 ` Jukka Larja
2016-07-21 12:22 Matthias Prager
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=667a14be-4a01-02f6-79f9-a8cd585f360d@gmail.com \
--to=ahferroin7@gmail.com \
--cc=dave@jikos.cz \
--cc=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=tom.kusmierz@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;
as well as URLs for NNTP newsgroup(s).