From: Anand Jain <anand.jain@oracle.com>
To: Joseph Dunn <jdunn14@gmail.com>, Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs seed question
Date: Fri, 13 Oct 2017 10:52:25 +0800 [thread overview]
Message-ID: <4a1ade13-3a2a-edfa-9918-70cef7e3cf5a@oracle.com> (raw)
In-Reply-To: <20171012104438.4304e99a@olive.ig.local>
>>> Not quite. While the seed device is still connected I would like to
>>> force some files over to the rw device. The use case is basically a
>>> much slower link to a seed device holding significantly more data than
>>> we currently need. An example would be a slower iscsi link to the seed
>>> device and a local rw ssd. I would like fast access to a certain subset
>>> of files, likely larger than the memory cache will accommodate. >>> If at a later time I want to discard the image as a whole I could
>>> unmount the file system or
Interesting. If you had not brought the idea of using seed device,
I would have still thinking about bcache device as a solution for
the above use case.
However bcache device won't help to solve the further use case
requirements as below..
>>> if I want a full local copy I could delete the
>>> seed-device to sync the fs. In the mean time I would have access to
>>> all the files, with some slower (iscsi) and some faster (ssd) and the
>>> ability to pick which ones are in the faster group at the cost of one
>>> content transfer.
I am thinking why not indeed leverage seed/sprout for this.
Let me see how I (or if anyone could) allocate time to experiment
on this.
Thanks for your use case !
-Anand
next prev parent reply other threads:[~2017-10-13 2:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 0:47 btrfs seed question Joseph Dunn
2017-10-12 4:18 ` Anand Jain
2017-10-12 13:20 ` Joseph Dunn
2017-10-12 14:32 ` Chris Murphy
2017-10-12 14:44 ` Joseph Dunn
2017-10-12 15:30 ` Chris Murphy
2017-10-12 15:50 ` Joseph Dunn
2017-11-03 8:03 ` Kai Krakow
2017-10-12 15:55 ` Austin S. Hemmelgarn
2017-10-13 2:52 ` Anand Jain [this message]
2017-11-03 7:56 ` Kai Krakow
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=4a1ade13-3a2a-edfa-9918-70cef7e3cf5a@oracle.com \
--to=anand.jain@oracle.com \
--cc=jdunn14@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).