From: Remi Gauvin <remi@georgianit.com>
To: Adam Borowski <kilobyte@angband.pl>, Nathan Dehnel <ncdehnel@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: SATA/SAS mixed pool
Date: Thu, 13 Dec 2018 05:39:46 -0500 [thread overview]
Message-ID: <60315740-e3e5-ed7f-a25b-6889932d0cfd@georgianit.com> (raw)
In-Reply-To: <20181213072905.ac352nclowixfhpt@angband.pl>
[-- Attachment #1.1.1: Type: text/plain, Size: 718 bytes --]
On 2018-12-13 02:29 AM, Adam Borowski wrote:
>
> For btrfs, a block device is a block device, it's not "racist".
> You can freely mix and/or replace. If you want to, say, extend a SD
> card with NBD to remote spinning rust, it works well -- tested :p
>
The possibility ff NBD certainly intrigues me, but I would be concerned
about the write barriers,, (needed to make sure cached writes are
committed to spinning rust in the correct order, so as to avoid
corruption in the case of interruption.
Assuming the underlaying block device on the remote device has a working
implementation, (as we know, not always a safe assumption...) does NBD
properly pass along the barriers commands/support?
[-- Attachment #1.1.2: remi.vcf --]
[-- Type: text/x-vcard, Size: 203 bytes --]
begin:vcard
fn:Remi Gauvin
n:Gauvin;Remi
org:Georgian Infotech
adr:;;3-51 Sykes St. N.;Meaford;ON;N4L 1X3;Canada
email;internet:remi@georgianit.com
tel;work:226-256-1545
version:2.1
end:vcard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2018-12-13 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 3:31 SATA/SAS mixed pool Nathan Dehnel
2018-12-13 4:07 ` Zia Nayamuth
2018-12-13 7:29 ` Adam Borowski
2018-12-13 10:39 ` Remi Gauvin [this message]
2018-12-13 12:48 ` Austin S. Hemmelgarn
2018-12-14 5:14 ` Duncan
2018-12-14 15:26 ` Adam Borowski
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=60315740-e3e5-ed7f-a25b-6889932d0cfd@georgianit.com \
--to=remi@georgianit.com \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=ncdehnel@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).