From: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: make-bcache's bucket size and block size values are ignored
Date: Tue, 9 Apr 2013 15:54:15 -0400 [thread overview]
Message-ID: <20130409195414.GA5680@redhat.com> (raw)
In-Reply-To: <20130409193521.GJ15749-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
On Tue, Apr 09 2013 at 3:35pm -0400,
Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:
> On Tue, Apr 09, 2013 at 10:07:36AM -0400, Mike Snitzer wrote:
> > Hey Kent,
> >
> > No matter what I specify via make-bcache's -b and -w args they are
> > always 512k and 512b respectively, e.g.:
> >
> > # make-bcache -B /dev/mapper/test-dev-174467 -C /dev/mapper/test-dev-24832 --cache_replacement_policy=fifo -b 2048k --writeback --discard
> > UUID: 3705b1d8-4b44-406c-abf2-594c0cb146be
> > Set UUID: a16dc554-c054-4a24-90fa-40f624e3a652
> > nbuckets: 8192
> > block_size: 1
> > bucket_size: 1024
> > nr_in_set: 1
> > nr_this_dev: 0
> > first_bucket: 1
> > UUID: 46a37bba-2582-4533-a95b-1eb29c71e53f
> > Set UUID: a16dc554-c054-4a24-90fa-40f624e3a652
> > nbuckets: 512
> > block_size: 1
> > bucket_size: 1024
> > nr_in_set: 1
> > nr_this_dev: 0
> > first_bucket: 1
> >
> > # cat /sys/block/bcache3/bcache/cache/bucket_size
> > 512k
> >
> > I can take a look at the make-bcache source in a bit but figured I'd let
> > you know sooner rather than later.
>
> Oh, it's because you specified the bucket size after the device. If you
> specify the devices last it'll work.
>
> So it's definitely unintuitive and semi broken, the reason it works that
> way is for formatting backing devices and cache devices at the same
> time; it walks through the options, and when it sees a device it formats
> it with the options seen so far.
OK, thanks for the insight.
> Right way to do it would be to make two passes...
Or just defer the formatting until all args are processed.
> I suppose I should just do that so it doesn't trip other people up.
Yeah, probably for the best.
Thanks.
prev parent reply other threads:[~2013-04-09 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:07 make-bcache's bucket size and block size values are ignored Mike Snitzer
[not found] ` <20130409140735.GA3984-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-04-09 19:35 ` Kent Overstreet
[not found] ` <20130409193521.GJ15749-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-04-09 19:54 ` Mike Snitzer [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=20130409195414.GA5680@redhat.com \
--to=snitzer-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.