linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Hlep hardware selection
Date: Thu, 18 Jul 2013 17:34:13 -0500	[thread overview]
Message-ID: <51E86D65.6020707@hardwarefreak.com> (raw)
In-Reply-To: <CAH3kUhHWQ3tNr843=oO+JacEG8uTvqhXsyx0WvN8Dk+F_tDGoA@mail.gmail.com>

On 7/18/2013 4:26 PM, Roberto Spadim wrote:
> Hi guys, i'm a bit distant from last hardware
> i need four disks (enterprise level ~ 120 to 300gb)
> two ssd (for cache via bcache,dmcache or flashcache ~ 120gb or less)
> and a raid controller card that i could use smartctl and others tools
> to check disk status
> 
> any help is welcome, i don't know if here is the better place to ask,
> or if anyone know some high level forum / list for hardware updates
> i need true fail safe disks (enterprise use), i'm talking about
> checksum of disk, silent error detection or maybe silent error prof

You've presented somewhat of a fairy land smorgasbord wish list, not an
actual set of requirements.  Maybe if provide an actual set of
requirements you'd get some real answers.  I.e.

My workload needs net capacity X, Y IOPS, and Z bandwidth.  I want to
use a real enterprise caliber RAID card with battery/flash backed write
cache, and I want to use enterprise class drives.  My budget is $AAAA.

Will the drives will be housed in an external SAS JBOD hot swap chassis
or in a hot swap SAS backplane in an existing server?  If you're not
using hot swap backplanes none of your "enterprise" aspirations are valid.

-- 
Stan



      reply	other threads:[~2013-07-18 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 21:26 Hlep hardware selection Roberto Spadim
2013-07-18 22:34 ` Stan Hoeppner [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=51E86D65.6020707@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=roberto@spadim.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).