From: Stan Hoeppner <stan@hardwarefreak.com>
To: Emmanuel Florac <eflorac@intellique.com>,
Dave Chinner <david@fromorbit.com>
Cc: Mike Dacre <mike.dacre@gmail.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Sudden File System Corruption
Date: Mon, 09 Dec 2013 21:39:52 -0600 [thread overview]
Message-ID: <52A68D08.8020505@hardwarefreak.com> (raw)
In-Reply-To: <20131209233028.27ee7154@galadriel.home>
On 12/9/2013 4:30 PM, Emmanuel Florac wrote:
> Le Tue, 10 Dec 2013 09:21:31 +1100 vous écriviez:
> Dave Chinner wrote:
>>
>> So, while the tech might be great, the benchmarks sucked at
>> demonstrating that.
It's pretty difficult to find comprehensive benchmark results,
especially for niche products such as CacheCade.
> And now that we have enhance-io, bcache and friends, I'm actually more
> confident of using these than some sort of hidden pseudo-hardware magic.
Enhance-IO is $295 per Linux server per year. Last I saw, Cleancache
isn't fully supported by XFS yet in a stable vanilla release. AFAIK
bcache isn't fully baked yet. Coupled with the fact that Mike seems to
be limited to the CentOS ecosystem, I figured CacheCade was his best
option at this time. It's been around a couple of years, works,
verified decent performance, and no additional kernel software is
required. And it's relatively easy to configure.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-10 3:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 2:55 Sudden File System Corruption Mike Dacre
2013-12-05 3:40 ` Dave Chinner
2013-12-05 3:46 ` Mike Dacre
2013-12-05 3:59 ` Dave Chinner
2013-12-05 8:10 ` Stan Hoeppner
[not found] ` <CAPd9ww9hsOFK6pxqRY-YtLLAkkJHCuSi1BaM4n9=2XTjNVAn2Q@mail.gmail.com>
2013-12-05 15:58 ` Fwd: " Mike Dacre
2013-12-06 8:58 ` Stan Hoeppner
[not found] ` <CAPd9ww8+W2VX2HAfxEkVN5mL1a_+=HDAStf1126WSE33Vb=VsQ@mail.gmail.com>
2013-12-06 23:15 ` Fwd: " Mike Dacre
2013-12-07 11:12 ` Stan Hoeppner
2013-12-07 18:36 ` Mike Dacre
2013-12-08 5:22 ` Stan Hoeppner
2013-12-08 15:03 ` Emmanuel Florac
2013-12-09 0:58 ` Stan Hoeppner
2013-12-09 1:40 ` Dave Chinner
2013-12-09 19:51 ` Stan Hoeppner
2013-12-09 22:21 ` Dave Chinner
2013-12-09 22:30 ` Emmanuel Florac
2013-12-10 3:39 ` Stan Hoeppner [this message]
2013-12-10 8:45 ` Emmanuel Florac
2013-12-09 22:24 ` Emmanuel Florac
2013-12-09 9:49 ` Emmanuel Florac
2013-12-05 17:40 ` Ben Myers
[not found] ` <20131205175053.GG1935@sgi.com>
[not found] ` <CAPd9ww9YFbMEe-dM96zHsbRJgQuBHfF=ipromch1Yw6SzPUftg@mail.gmail.com>
[not found] ` <20131206002308.GS10553@sgi.com>
[not found] ` <CAPd9ww8XDzGbSZsEEoCmSuJ+KBYUWqHeRON1sFr6bG1fZ6af7w@mail.gmail.com>
[not found] ` <20131206225612.GU10553@sgi.com>
2013-12-06 23:15 ` Mike Dacre
2013-12-08 22:20 ` Dave Chinner
2013-12-09 19:04 ` Eric Sandeen
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=52A68D08.8020505@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=david@fromorbit.com \
--cc=eflorac@intellique.com \
--cc=mike.dacre@gmail.com \
--cc=xfs@oss.sgi.com \
/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