From: Jukka Larja <roskakori@aarghimedes.fi>
To: Matthias Prager <linux@matthiasprager.de>,
Henk Slager <eye1tm@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Status of SMR with BTRFS
Date: Mon, 18 Jul 2016 21:49:47 +0300 [thread overview]
Message-ID: <578D24CB.8030106@aarghimedes.fi> (raw)
In-Reply-To: <5c31c6fd-5f4a-0fb6-07c9-a56964f30262@matthiasprager.de>
18.7.2016, 0.44, Matthias Prager kirjoitti:
> the Seagate SMR drives are fast enough to handle Gbit-LAN
> speeds if they are served mostly large sequential chunks by the file
> system, which f2fs actually manages to do (cold storage in my scenario
> too). Btrfs does too many scattered writes for this to work without
> bandages (i.e. caching or snapshotting) (although I do see the advantage
> in having checksums for data which you write once and then read like
> once every year).
I have two 8 TB Seagate Archive drives (which did cause me lots of extra
work, before I got everything patched and/or hardware to work correctly) in
Btrfs raid1[0] configuration. They serve as backup for DVR (and for testing,
as a backup of a backup of my Windows laptop) with around 4 TB of
recordings. Original rsync ran at about network speed. Both drives were
writing a bit over 100 MB/s for the whole time.
Backups are updated once per day, few GBs of recordings and around 5000
small files from laptop changed, removed or created. I'm sort of waiting for
something to explode, but so far it seems to be working fine. Maybe I'll put
some real backups there some day.
[0] No need to tell me this shouldn't be done. It's for testing purposes.
--
...Elämälle vierasta toimintaa...
Jukka Larja, Roskakori@aarghimedes.fi
"Later subverted by himself; when he tried to march through the Makran
desert *SPOILER ALERT*. Ouch..."
"Buddy, Alexander is literally ancient history. There are limits to the
spoiler tag."
- TV Tropes Wiki, Never Tell Me The Odds, Aleksanteri suuresta -
next prev parent reply other threads:[~2016-07-18 18:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 8:26 Status of SMR with BTRFS Matthias Prager
2016-07-17 20:10 ` Henk Slager
2016-07-17 21:44 ` Matthias Prager
2016-07-18 18:49 ` Jukka Larja [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-21 12:22 Matthias Prager
2016-07-15 18:29 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
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
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=578D24CB.8030106@aarghimedes.fi \
--to=roskakori@aarghimedes.fi \
--cc=eye1tm@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux@matthiasprager.de \
/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).