public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: XFS internal error (memory corruption)
Date: Wed, 06 Jul 2011 17:04:42 -0500	[thread overview]
Message-ID: <4E14DBFA.3040302@hardwarefreak.com> (raw)
In-Reply-To: <20110706080505.GA2354@infradead.org>

On 7/6/2011 3:05 AM, Christoph Hellwig wrote:
> On Wed, Jul 06, 2011 at 05:22:21PM +1000, Dave Chinner wrote:
>> Unless you have a good sized chunk of BBWC in front of your disks,
>> in which case internal logs are just as fast. In fact, internal logs
>> can are often faster in this case because an internal log on a 12
>> disk RAID6 array can sink a whole log more bandwidth than an external
>> log on a 2-disk RAID0 mirror.....
>>
>> At least, that's what my hardware tells me. ;)
> 
> Sure, a nice BBWC setup will give you good results.  But it's generally
> much more expensive than a simple setup with a raid5 or 6 and a mirror for
> the log device.

If you're talking consumer grade gear, well, sure, as there is no such
thing as a consumer hardware RAID card.  In the world of branded OEM
'enterprise' gear, you can get a BBWC RAID card solution for little more
than two drives.  Are most XFS admins running consumer or enterprise
grade gear?

LSI 9260-4i w/512MB BBWC     = $485 USD
Intel RES2SV24024P expander  = $280 USD
Total                        = $765 USD

2 HP 146GB 10kRPM SAS drives = $520 USD.

I threw in the expander as this LSI card is thoroughly limited with only
4 ports.  It's also cheaper going this route than buying the sister card
with 8 ports, yet with the same performance, and 12 more total ports.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-07-06 22:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05  6:03 XFS internal error (memory corruption) Török Edwin
2011-07-05 13:09 ` Dave Chinner
2011-07-05 13:38   ` Török Edwin
2011-07-06  4:04     ` Dave Chinner
2011-07-06  7:07       ` Christoph Hellwig
2011-07-06  7:22         ` Dave Chinner
2011-07-06  8:05           ` Christoph Hellwig
2011-07-06 22:04             ` Stan Hoeppner [this message]
2011-07-06 19:30           ` Stan Hoeppner
2011-07-06 23:52             ` Dave Chinner

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=4E14DBFA.3040302@hardwarefreak.com \
    --to=stan@hardwarefreak.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