From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Graham Cobb <g.btrfs@cobb.uk.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: experiences running btrfs on external USB disks?
Date: Tue, 4 Dec 2018 08:55:24 -0500 [thread overview]
Message-ID: <bf90f799-2202-f266-c829-801c22b81ac6@gmail.com> (raw)
In-Reply-To: <d891096f-04c5-cf4b-cfb6-ba873b1ff72f@cobb.uk.net>
On 2018-12-04 08:37, Graham Cobb wrote:
> On 04/12/2018 12:38, Austin S. Hemmelgarn wrote:
>> In short, USB is _crap_ for fixed storage, don't use it like that, even
>> if you are using filesystems which don't appear to complain.
>
> That's useful advice, thanks.
>
> Do you (or anyone else) have any experience of using btrfs over iSCSI? I
> was thinking about this for three different use cases:
>
> 1) Giving my workstation a data disk that is actually a partition on a
> server -- keeping all the data on the big disks on the server and
> reducing power consumption (just a small boot SSD in the workstation).
>
> 2) Splitting a btrfs RAID1 between a local disk and a remote iSCSI
> mirror to provide redundancy without putting more disks in the local
> system. Of course, this would mean that one of the RAID1 copies would
> have higher latency than the other.
>
> 3) Like case 1 but actually exposing an LVM logical volume from the
> server using iSCSI, rather than a simple disk partition. I would then
> put both encryption and RAID running on the server below that logical
> volume.
>
> NBD could also be an alternative to iSCSI in these cases as well.
>
> Any thoughts?
I've not run it over iSCSI (I tend to avoid that overly-complicated
mess), but I have done it over NBD and ATAoE, as well as some more
exotic arrangements, and it's really not too bad. The important part is
making sure your block layer and all the stuff under it are reliable,
and USB is not.
prev parent reply other threads:[~2018-12-04 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 5:37 experiences running btrfs on external USB disks? Tomasz Chmielewski
2018-12-04 5:59 ` Chris Murphy
2018-12-04 6:13 ` Tomasz Chmielewski
2018-12-04 12:38 ` Austin S. Hemmelgarn
2018-12-04 13:37 ` Graham Cobb
2018-12-04 13:55 ` Austin S. Hemmelgarn [this message]
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=bf90f799-2202-f266-c829-801c22b81ac6@gmail.com \
--to=ahferroin7@gmail.com \
--cc=g.btrfs@cobb.uk.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).