From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Felix Homann <linuxaudio@showlabor.de>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs on bcache
Date: Thu, 01 May 2014 07:33:45 -0400 [thread overview]
Message-ID: <53623119.8070809@gmail.com> (raw)
In-Reply-To: <CAFz=ag4x7TY5AYpx-Oubi6S-9xR7bXRBYK3zLihMpgpmSVOi3w@mail.gmail.com>
On 2014-04-30 14:16, Felix Homann wrote:
> Hi,
> a couple of months ago there has been some discussion about issues
> when using btrfs on bcache:
>
> http://thread.gmane.org/gmane.comp.file-systems.btrfs/31018
>
> From looking at the mailing list archives I cannot tell whether or not
> this issue has been resolved in current kernels from either bcache's
> or btrfs' side.
>
> Can anyone tell me what's the current state of this issue? Should it
> be safe to use btrfs on bcache by now?
In all practicality, I don't think anyone who frequents the list knows.
I do know that there are a number of people (myself included) who avoid
bcache in general because of having issues with seemingly random kernel
OOPSes when it is linked in (either as a module or compiled in), even
when it isn't being used. My advice would be to just test it with some
non-essential data (maybe set up a virtual machine?).
next prev parent reply other threads:[~2014-05-01 11:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 18:16 btrfs on bcache Felix Homann
2014-05-01 11:33 ` Austin S Hemmelgarn [this message]
2014-05-01 12:02 ` Fwd: " Felix Homann
2014-05-01 17:32 ` Peter Kieser
-- strict thread matches above, loose matches on Subject: below --
2014-08-20 20:17 raphead
[not found] <1731942750.1162128.1406757898913.JavaMail.ngmail@webmail06.arcor-online.net>
2014-07-31 15:35 ` dptrash
2014-08-01 1:55 ` Duncan
2014-07-30 22:04 dptrash
2014-07-30 23:01 ` Larkin Lowrey
2014-08-04 12:57 ` Fábio Pfeifer
2013-12-18 17:17 eb
2013-12-19 19:04 ` Fábio Pfeifer
2013-12-19 19:05 ` Fábio Pfeifer
2013-12-20 22:26 ` Henry de Valence
2013-12-19 19:59 ` Chris Mason
2013-12-20 12:36 ` eb
2013-12-20 12:42 ` Fábio Pfeifer
2013-12-20 15:46 ` Chris Mason
2013-12-24 16:44 ` Fábio Pfeifer
2013-12-24 16:44 ` Fábio Pfeifer
2014-01-06 23:37 ` Kent Overstreet
2014-01-08 19:35 ` Chris Mason
2014-01-08 21:13 ` Kent Overstreet
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=53623119.8070809@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linuxaudio@showlabor.de \
/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.