On 5/15/2014 11:18 AM, Peter Kieser wrote:
On 2014-05-15 1:02 AM, Francis Moreau wrote:
Eventually I would suggest to mark bcache as an experimental thing since
it's really not ready for production, just take a look at the bcache
mailing list to see why. At least people won't be disappointed when
they'll use bcache and see ton of koops.
I'm going to second this request to mark bcache as experimental. XFS
performance has been stunted (almost DoS condition) since 3.10.4,
btrfs doesn't currently work and Kent is leaving it up to the btrfs
team to fix the bugs in either bcache or btrfs. Multiple
deadlocks/interruptible sleeps and corruption.
-Peter
Greetings,
First let me say I can empathize with your struggles and agree
these bugs do need to be resolved. There's been a lot of work going into
resolving the issues without avail. Sometimes the bugs are other teams
issues as they are not following system that is outlined.
I'd like to represent the other side of the coin here. I'm aware
of numerous storage solution situations where bcache has been stable and
in production for 18-24 months. I myself have over 20 systems in place
with numerous file systems running without issues. There are storage
vendors in the process of introducing into their next release. If it all
possible, lets try to reach out to other developers and help Kent with
getting these few issues tracked down. They are obviously tricky. Again
it is up to others to decide.
Thanks,
Ross Anderson
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
