From: Christopher James Halse Rogers <chris@cooperteam.net>
To: Martin McClure <martin.mcclure@gemtalksystems.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
linux-bcache@vger.kernel.org
Subject: Re: bcachefs with cache device and backing device
Date: Fri, 20 May 2016 10:44:16 +1000 [thread overview]
Message-ID: <1463705056.3733.2@mail.cooperteam.net> (raw)
In-Reply-To: <573E5D24.604@gemtalksystems.com>
On Fri, May 20, 2016 at 10:41 AM, Martin McClure
<martin.mcclure@gemtalksystems.com> wrote:
> On 05/17/2016 10:41 PM, Kent Overstreet wrote:
>> Actually, I just tested and mounting multile devices directly
>> _does_ work - you
>> just pass a colon separated list of devices to mount:
>>
>> mount -t bcache /dev/sdb:/dev/sdc /mnt
>>
>> I could have sworn this was broken, but worked just now...
>
> This works for me. Thanks for the feedback!
>
> For any others wanting to walk this path in the near future, here's
> the
> entire sequence that is working for me (as of kernel and tools pulled
> on
> 2016-05-13):
>
> bcache format --tier 0 --bucket=512k --cache_mode=writeback \
> -C /dev/nvme0n1 \
> --tier 1 -C /dev/sdd1
>
> echo /dev/sdd1 > /sys/fs/bcache/register
> echo /dev/nvme0n1 > /sys/fs/bcache/register
You should be able to remove these steps, I think?
>
> mount -t bcache /dev/nvme0n1:/dev/sdd1 /mnt/whatever
If you've pre-registered, you should be able to just
mount -t bcache /dev/nvme0n1 /mnt/whatever
or, entirely equivalently:
mount -t bcache /dev/sdd1 /mnt/whatever
next prev parent reply other threads:[~2016-05-20 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 1:50 bcachefs with cache device and backing device Martin McClure
2016-05-13 4:36 ` Kent Overstreet
2016-05-13 4:37 ` Martin McClure
2016-05-18 2:46 ` Martin McClure
2016-05-18 4:01 ` Kent Overstreet
2016-05-18 5:06 ` Christopher James Halse Rogers
2016-05-18 5:41 ` Kent Overstreet
2016-05-20 0:41 ` Martin McClure
2016-05-20 0:44 ` Christopher James Halse Rogers [this message]
2016-05-20 1:18 ` Martin McClure
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=1463705056.3733.2@mail.cooperteam.net \
--to=chris@cooperteam.net \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=martin.mcclure@gemtalksystems.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).