From: "Mickaël Canévet" <canevet@embl.fr>
To: ceph-devel@vger.kernel.org
Subject: Multiple disks per server.
Date: Tue, 04 May 2010 14:18:25 +0200 [thread overview]
Message-ID: <4BE01091.7040103@embl.fr> (raw)
Hi,
I'm testing ceph on 4 old servers.
As there is more then one disk per server available for data (2 with 6
disks and 2 with 10 disks for a total of 32 disks over 4 nodes), I was
wondering how to define OSDs.
I have choice between one OSD per disk (32 OSDs on the cluster) or one
OSD per server with one btrfs filesystem over all disks of the server (4
OSDs on the cluster). Which one is the best solution ?
In the first case, if I lose one disk, I lose only a small part of
available space. In the other case, if I lose one disk, I lose the whole
server (as btrfs filesystem is in stripping) much more space.
On the other hand, if I lose the whole server in the first case, I can
lose all replicates of a data because they may be on two different OSD
on the same server.
Is there a way to define OSD groups so that we can be sure that 2
replicates are not on OSDs of the same group (could be usefull for
multiple OSDs per server, but also mutliple server per computing room -
if I lose one whole room, a lot of server, I will be sure that I have
not lost every replicates).
Thanks a lot.
Mickaël
--
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
next reply other threads:[~2010-05-04 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 12:18 Mickaël Canévet [this message]
2010-05-04 12:34 ` Multiple disks per server Wido den Hollander
2010-05-04 17:37 ` Sage Weil
2010-05-06 3:18 ` Cláudio Martins
2010-05-06 4:02 ` Sage Weil
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=4BE01091.7040103@embl.fr \
--to=canevet@embl.fr \
--cc=ceph-devel@vger.kernel.org \
/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.