public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul B. Henson" <henson-HInyCGIudOg@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: good bcache use case?
Date: Mon, 14 Oct 2013 15:49:55 -0700	[thread overview]
Message-ID: <1005c01cec92f$b61b2040$225160c0$@acm.org> (raw)

I'm building a server to do some kvm virtualization. Right now, I've got 4
2TB Western Digital RE4 hard disks, and 2 256G Samsung 840 Pro SSD's.

My initial intent was to build a RAID10 from the 2 TB hard disks, and a
RAID1 from the SSD's, have two separate lvm volume groups, and manually
partition file systems between them based on the need for performance.

I was wondering if it would make a good use case for bcache to instead use
the 256G RAID1 as a cache for backing the 4TB RAID10? Ideally that would
enhance the performance of all I/O, rather than just whatever filesystems
were manually placed on the SSD's in my original plan.

From my research so far, it seems that bcache in the 3.10 kernel is
considered stable enough for production, and there shouldn't be any issues
using software RAID for the backing and cache devices? Even with writeback
enabled?

Any gotchas or pointers for this potential deployment?

Thanks much.

             reply	other threads:[~2013-10-14 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 22:49 Paul B. Henson [this message]
2013-10-15 15:00 ` good bcache use case? matthew patton
     [not found]   ` <1381849203.67736.YahooMailNeo-XYahOdtEMNn35Xbc4wGBzZOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-10-15 19:12     ` Paul B. Henson
2013-10-15 21:12       ` Gabriel de Perthuis
     [not found]         ` <525DAFA3.4060709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-16 19:29           ` Paul B. Henson

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='1005c01cec92f$b61b2040$225160c0$@acm.org' \
    --to=henson-hinycgiudog@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox