From: Kent Overstreet <kent.overstreet@gmail.com>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: marcin@mejor.pl, linux-bcache@vger.kernel.org
Subject: Re: How to create bcachefs?
Date: Wed, 24 Aug 2016 15:52:06 -0800 [thread overview]
Message-ID: <20160824235206.tq75ghe5n5gjciqm@kmo-pixel> (raw)
In-Reply-To: <alpine.LRH.2.11.1608241611270.10662@mail.ewheeler.net>
On Wed, Aug 24, 2016 at 04:12:22PM -0700, Eric Wheeler wrote:
> On Wed, 24 Aug 2016, marcin@mejor.pl wrote:
>
> > W dniu 24.08.2016 o 08:52, Kent Overstreet pisze:
> > [...]
> >
> > Hi!
> > > Hey, sorry for the long delay, been sick past several days.
> >
> > I was afraid that I'm asking to easy question:) And I hope everything is
> > fine with you now!
> >
> >
> > > The way arguments
> > > were passed to bcache format was a holdover from old style make-bcache, and
> > > didn't make much sense for bcachefs - -C was used for all devices, and
> > > --tier
> > > specifies fast devices and slow devices.
> > >
> > > I finally got around to redoing the option parsing so we don't need the -C
> > > argument today - update your bcache tools, and the command you want is now:
> > >
> > > bcache format --tier 0 /dev/sde1 --tier 1 /dev/sdd1
>
> Neat! How many performance tiers are (will be) supported? Arbitrary?
Currently the code just handles two, but the on disk format allows for up to 16.
next prev parent reply other threads:[~2016-08-25 8:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 18:07 How to create bcachefs? marcin
2016-08-24 6:52 ` Kent Overstreet
2016-08-24 21:21 ` marcin
2016-08-24 23:12 ` Eric Wheeler
2016-08-24 23:52 ` Kent Overstreet [this message]
2016-08-24 23:50 ` Kent Overstreet
2016-08-25 0:03 ` Christopher James Halse Rogers
2016-08-25 9:21 ` Marcin Mirosław
2016-08-25 11:09 ` Christopher James Halse Rogers
2016-08-25 12:11 ` Marcin Mirosław
2016-08-26 1:06 ` Christopher James Halse Rogers
2016-08-26 1:48 ` Eric Wheeler
2016-08-26 8:23 ` Marcin Mirosław
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=20160824235206.tq75ghe5n5gjciqm@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=bcache@lists.ewheeler.net \
--cc=linux-bcache@vger.kernel.org \
--cc=marcin@mejor.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.