From: "Paul B. Henson" <henson-HInyCGIudOg@public.gmane.org>
To: 'Gabriel de Perthuis' <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: good bcache use case?
Date: Wed, 16 Oct 2013 12:29:30 -0700 [thread overview]
Message-ID: <04b801cecaa6$0ad387e0$207a97a0$@acm.org> (raw)
In-Reply-To: <525DAFA3.4060709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> From: Gabriel de Perthuis [mailto:g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
> Sent: Tuesday, October 15, 2013 2:12 PM
>
> 3.10.x and 3.11.y stable kernels have been getting bcache backports
[...]
> that introduced the crash was fixing a more serious bug. Stopping here
> because the mailing list is starting to feel like Groundhog day.
Sorry, I did do some specific searching on the mailing list and a quick
review of recent traffic, don't mean to make you guys rehash stuff.
3.10.16 was just released this week, does that contain backports for all
known serious issues and would be considered suitable for production
deployment?
> but since LVM can do raid and a single cache can cache multiple devices,
I've seen references to raid using lvm (as opposed to lvm over md raid), but
it's never really been clear to me whether that is considered an alternative
to md raid, or a replacement, or whether it's better to do raid within lvm
rather than layering lvm on top of md raid. At this point, I'm considerably
more familiar with md raid so I've just been sticking with that.
Thanks much.
prev parent reply other threads:[~2013-10-16 19:29 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
2013-10-15 21:12 ` Gabriel de Perthuis
[not found] ` <525DAFA3.4060709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-16 19:29 ` Paul B. Henson [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='04b801cecaa6$0ad387e0$207a97a0$@acm.org' \
--to=henson-hinycgiudog@public.gmane.org \
--cc=g2p.code-Re5JQEeQqe8AvxtiuMwx3w@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