linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin McClure <martin.mcclure@gemtalksystems.com>
To: Christopher James Halse Rogers <chris@cooperteam.net>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
	linux-bcache@vger.kernel.org
Subject: Re: bcachefs with cache device and backing device
Date: Thu, 19 May 2016 18:18:46 -0700	[thread overview]
Message-ID: <573E65F6.9090405@gemtalksystems.com> (raw)
In-Reply-To: <1463705056.3733.2@mail.cooperteam.net>

On 05/19/2016 05:44 PM, Christopher James Halse Rogers wrote:
>>
>>   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?

Yes, I don't seem to need those.

> 
>>
>>   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
> 

Yes. Looks like I need to *either* explicitly pre-register the devices
*or* specify them both in the mount command.

Thanks for the clarification.

The option that I'm going with for now is:

  bcache format --tier 0 --bucket=512k --cache_mode=writeback \
      -C /dev/nvme0n1 \
      --tier 1 -C /dev/sdd1

  mount -t bcache /dev/nvme0n1:/dev/sdd1 /mnt/whatever

since that shows me both devices in the output of "mount", reminding me
and anyone else trying to figure out what's going on with this machine
that both devices are involved in this filesystem.

Regards,

-Martin

      reply	other threads:[~2016-05-20  1:18 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
2016-05-20  1:18               ` Martin McClure [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=573E65F6.9090405@gemtalksystems.com \
    --to=martin.mcclure@gemtalksystems.com \
    --cc=chris@cooperteam.net \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@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).