All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: "emyr.james" <emyr.james@sussex.ac.uk>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Looking to Use Ceph
Date: Thu, 03 Jan 2013 15:38:46 +0100	[thread overview]
Message-ID: <50E597F6.6000609@widodh.nl> (raw)
In-Reply-To: <50E579AF.10206@sussex.ac.uk>

On 01/03/2013 01:29 PM, emyr.james wrote:
> Hi,
>
> I'm thinking of starting to use ceph initially for evaluation...seeing
> how it compares to our existing lustre file system.
> One thing that I would like confirmation of is how ceph stores large
> files. If I store a large file in CephFS is it automatically split up
> into chunks with the various chunks stored and replicated automatically
> across the whole cluster, or does it store the whole file as one object
> on one individial OSD and then has individual replicants of the whole
> file on a small number of other OSD's ? What is the typical block size
> used if files are split up....can this be configured ?
>

Files are by default striped in 4MB blocks which are then distributed 
over the OSDS and replicated.

A 1G file will thus result in 256 different object distributed and 
replicated through your cluster.

You can configure the stripe-size with the "cephfs" tool on a client.

Note: CephFS hasn't got the attention like RADOS and RBD got, so you 
might run into some weird situations.

Wido

> Regards,
>
> Emyr
>
> --
> 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:[~2013-01-03 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 12:29 Looking to Use Ceph emyr.james
2013-01-03 14:38 ` Wido den Hollander [this message]
2013-01-03 14:43 ` 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=50E597F6.6000609@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=emyr.james@sussex.ac.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.