From: Joao Eduardo Luis <joao.luis@inktank.com>
To: charles L <charlesboy009@hotmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: testing ceph
Date: Thu, 31 Oct 2013 10:55:56 +0000 [thread overview]
Message-ID: <5272373C.4020906@inktank.com> (raw)
In-Reply-To: <DUB116-W8372DACD4F54B9145260E4E00B0@phx.gbl>
On 10/31/2013 04:54 AM, charles L wrote:
> Hi,
> Pls is this a good setup for a production environment test of ceph? My focus is on the SSD ... should it be partitioned(sdf1,2 ,3,4) and shared by the four OSDs on a host? or is this a better configuration for the SSD to be just one partition(sdf1) while all osd uses that one partition?
> my setup:
> - 6 Servers with one 250gb boot disk for OS(sda),
> four-2Tb Disks each for the OSDs i.e Total disks = 6x4 = 24 disks (sdb -sde)
> and one-60GB SSD for Osd Journal(sdf).
> -RAM = 32GB on each server with 2 GB network link.
> hostname for servers: Server1 -Server6
Charles,
What you are describing on the ceph.conf below is definitely not a good
idea. If you really want to use just one SSD and share it across
multiple OSDs, then you have two possible approaches:
- partition that disk and assign a *different* partition to each OSD; or
- keep only one partition, format it with some filesystem, and assign a
*different* journal file within that fs to each OSD.
What you are describing has you using the same partition for all OSDs.
This will likely create issues due to multiple OSDs writing and reading
from a single journal. TBH I'm not familiar enough with the journal
mechanism to know whether the OSDs will detect that situation.
-Joao
>
> [osd.0]
> host = server1
> devs = /dev/sdb
> osd journal = /dev/sdf1
> [osd.1]
> host = server1
> devs = /dev/sdc
> osd journal = /dev/sdf2
>
> [osd.3]
> host = server1
> devs = /dev/sdd
> osd journal = /dev/sdf2
>
> [osd.4]
> host = server1
> devs = /dev/sde
> osd journal = /dev/sdf2
> [osd.5]
> host = server2
> devs = /dev/sdb
> osd journal = /dev/sdf2
> ...
> [osd.23]
> host = server6
> devs = /dev/sde
> osd journal = /dev/sdf2
>
> Thanks. --
> 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
>
--
Joao Eduardo Luis
Software Engineer | http://inktank.com | http://ceph.com
next prev parent reply other threads:[~2013-10-31 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 4:54 testing ceph charles L
2013-10-31 10:55 ` Joao Eduardo Luis [this message]
[not found] ` <5272373C.4020906-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2013-11-04 15:25 ` charles L
[not found] ` <DUB116-W91D38BDD6BED25D0F26267E0F60-MsuGFMq8XAE@public.gmane.org>
2013-11-04 15:56 ` Trivedi, Narendra
2013-11-04 16:55 ` [ceph-users] " Alfredo Deza
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=5272373C.4020906@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=charlesboy009@hotmail.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 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.