public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul B. Henson" <henson-HInyCGIudOg@public.gmane.org>
To: 'matthew patton'
	<pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>,
	'Dirk Geschke' <dirk-WMiem5eIfR0n5izryJqWLw@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: bcache not working on large files?
Date: Tue, 22 Oct 2013 19:06:28 -0700	[thread overview]
Message-ID: <0cde01cecf94$7dccdb50$796691f0$@acm.org> (raw)
In-Reply-To: <1382480829.46079.YahooMailNeo-XYahOdtEMNkbWpotXP+qY5OW+3bF1jUfVpNB7YpNyf8@public.gmane.org>

> From: matthew patton
> Sent: Tuesday, October 22, 2013 3:27 PM
>
> 'busted' in this case means errors on write. If the device disappears and
is no
> longer readable, then sure any un-committed blocks are gone and your
> filesystem/file is broken.

In other words, if you care about your data, don't use a nonredundant cache
device in writeback mode 8-/. I'm tentatively planning to use an md mirror
of two 256G SSD's to front end a raid10 of 4 2TB HD's, I'm still in the
investigate stage but hopefully will get to prototyping soon.
 
> If you're not running kernel 3.11.5 (or 3.11.4 with *all* the bcache
fixes)
> you're wasting your time.

Is there an intention to port all of these fixes back to an LTS 3.10 kernel,
or if you're going to run in production you're pretty much committed to the
latest stable?

Thanks.

  parent reply	other threads:[~2013-10-23  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22  7:08 bcache not working on large files? Dirk Geschke
     [not found] ` <20131022070830.GA20286-TGNR7510c4H9eX/OD4jYIkzuTB+3w3uf@public.gmane.org>
2013-10-22 17:35   ` Rolf Fokkens
     [not found]     ` <5266B774.6040202-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-10-22 18:03       ` Dirk Geschke
     [not found]         ` <20131022180316.GA24473-TGNR7510c4H9eX/OD4jYIkzuTB+3w3uf@public.gmane.org>
2013-10-22 21:11           ` matthew patton
     [not found]             ` <1382476284.36900.YahooMailNeo-XYahOdtEMNlRBbKmAC7my5OW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-10-22 21:45               ` Dirk Geschke
     [not found]                 ` <20131022214553.GC26186-TGNR7510c4H9eX/OD4jYIkzuTB+3w3uf@public.gmane.org>
2013-10-22 22:27                   ` matthew patton
     [not found]                     ` <1382480829.46079.YahooMailNeo-XYahOdtEMNkbWpotXP+qY5OW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-10-23  2:06                       ` Paul B. Henson [this message]
2013-10-23 14:47                   ` Dirk Geschke
2013-10-22 22:16               ` matthew patton

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='0cde01cecf94$7dccdb50$796691f0$@acm.org' \
    --to=henson-hinycgiudog@public.gmane.org \
    --cc=dirk-WMiem5eIfR0n5izryJqWLw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox