All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul B. Henson" <henson-HInyCGIudOg@public.gmane.org>
To: 'matthew patton'
	<pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>,
	linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: good bcache use case?
Date: Tue, 15 Oct 2013 12:12:43 -0700	[thread overview]
Message-ID: <038e01cec9da$8a19e750$9e4db5f0$@acm.org> (raw)
In-Reply-To: <1381849203.67736.YahooMailNeo-XYahOdtEMNn35Xbc4wGBzZOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>

> From: matthew patton [mailto:pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org]
> Sent: Tuesday, October 15, 2013 8:00 AM
>
> Anything shy of the official linux 3.11.5 kernel release has several
time-bomb
> bugs.

Hmm, given 3.10 is an LTS kernel presumably these bug fixes would be back
ported? I suppose it would just be a matter of making sure for a given
3.10.x that they had been.

> personally would be a bit circumspect in calling it fully production
ready. I
> don't believe there are any known significant bugs but with the recent
flurry
> of fixes I'd liken it's solidity as more pudding rather than cake.

Well, that's not exactly a ringing endorsement :). I suppose I could always
stick with plan A and migrate to bcache later, it should be easy enough to
pvmove everything off of the SSD raid1, pvremove it, and then with a little
downtime convert the raid10 to a backing store and the SSD raid1 to a cache.

Thanks for the opinions.

  parent reply	other threads:[~2013-10-15 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 22:49 good bcache use case? Paul B. Henson
2013-10-15 15:00 ` matthew patton
     [not found]   ` <1381849203.67736.YahooMailNeo-XYahOdtEMNn35Xbc4wGBzZOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-10-15 19:12     ` Paul B. Henson [this message]
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='038e01cec9da$8a19e750$9e4db5f0$@acm.org' \
    --to=henson-hinycgiudog@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pattonme-/E1597aS9LQAvxtiuMwx3w@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.