CEPH filesystem development
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: Jonathan Proulx <jon@csail.mit.edu>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ideal hardware spec?
Date: Thu, 23 Aug 2012 11:59:52 +0200	[thread overview]
Message-ID: <5035FF18.3030209@widodh.nl> (raw)
In-Reply-To: <20120822154615.GF10015@csail.mit.edu>

On 08/22/2012 05:46 PM, Jonathan Proulx wrote:
> On Wed, Aug 22, 2012 at 04:17:23PM +0200, Wido den Hollander wrote:
>
> :On 08/22/2012 03:55 PM, Jonathan Proulx wrote:
>
> :You can also use the USB sticks[0] from Stec, they have servergrade
> :onboard USB sticks for these kind of applications.
>
> Those look quite interesting.
>

They should be much more reliable than regular USB sticks due to their 
SLC memory.

You could also take a look at these: 
http://www.transcend-info.com/industry/products_details.asp?CatNo=2&SerNo=14&ModNo=28&Func1No=1

> :A couple of questions still need to be answered though:
> :* Which OS are you planning on using? Ubuntu 12.04 is recommended
>
> Ubuntu 12.04 is our current preferred OS
>

That should work fine.

> :* Which filesystem do you want to use underneath the OSDs?
>
> Whatever I can get to work best in testing :)
>
> Since this is for a research platform not a product I'd likely start with
> BTRFS and see if it is "stable enough" and "performant enough" with
> fall back to XFS if needed
>

BTRFS is indeed the best in terms of features. I'd recommend using a 
recent kernel like 3.5.

Wido

> -Jon
>
> :Wido
> :
> :[0]: http://www.stec-inc.com/product/ufm.php
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2012-08-23  9:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 13:55 Ideal hardware spec? Jonathan Proulx
2012-08-22 14:17 ` Wido den Hollander
2012-08-22 14:39   ` Stephen Perkins
2012-08-23  8:24     ` Wido den Hollander
2012-08-24 14:17       ` Stephen Perkins
2012-08-24 14:41         ` Joe Landman
2012-08-24 15:05         ` Mark Nelson
2012-08-24 16:30           ` Sławomir Skowron
2012-08-24 18:12           ` Wido den Hollander
2012-08-24 18:23             ` Mark Nelson
2012-08-27 18:05               ` Stephen Perkins
2012-08-27 22:33                 ` Wido den Hollander
     [not found]             ` <00ae01cd823e$84e2ed20$8ea8c760$@netmass.com>
2012-08-25 11:48               ` Wido den Hollander
2012-08-24 16:12         ` Tommi Virtanen
2012-08-24 18:09         ` Wido den Hollander
2012-08-22 15:46   ` Jonathan Proulx
2012-08-23  9:59     ` Wido den Hollander [this message]
     [not found]       ` <CABYiri_-73UyTKHcHWDZdjqb=rozjraVzxd166NZV2ir53tduA@mail.gmail.com>
2012-08-26 11:15         ` Wido den Hollander
2012-08-26 13:29           ` Mark Nelson
2012-08-22 14:41 ` Mark Nelson
2012-08-28  0:02   ` Curtis C.
2012-08-28  1:18     ` Mark Nelson

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=5035FF18.3030209@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jon@csail.mit.edu \
    /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