From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Wido den Hollander <wido@widodh.nl>
Cc: Travis Rhoden <trhoden@gmail.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: problems creating new ceph cluster when using journal on block device
Date: Thu, 08 Nov 2012 21:24:14 +1300 [thread overview]
Message-ID: <509B6C2E.2050708@catalyst.net.nz> (raw)
In-Reply-To: <509B6883.4010406@widodh.nl>
On 08/11/12 21:08, Wido den Hollander wrote:
>
>
> On 08-11-12 08:29, Travis Rhoden wrote:
>> Hey folks,
>>
>> I'm trying to set up a brand new Ceph cluster, based on v0.53. My
>> hardware has SSDs for journals, and I'm trying to get mkcephfs to
>> intialize everything for me. However, the command hangs forever and I
>> eventually have to kill it.
>>
>> After poking around a bit, it's clear that the problem has something
>> to do with the journal. If I comment out the journal in ceph.conf,
>> the commands proceed just find. This is the first time I've tried to
>> throw a journal on a block device rather than a file, so maybe I've
>> done something wrong with that.
>>
>> Here is the info from ceph.conf:
>>
>>
>> [osd]
>> osd journal size = 4000
>
> Not sure if this is the problem, but when using a block device you don't
> have to specify the size for the journal.
Also might be useful to know make/model of ssd, plus motherboard
make/model (in case commenting out size does not fix)!
Regards
Mark
next prev parent reply other threads:[~2012-11-08 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 7:29 problems creating new ceph cluster when using journal on block device Travis Rhoden
2012-11-08 8:08 ` Wido den Hollander
2012-11-08 8:24 ` Mark Kirkwood [this message]
2012-11-08 15:01 ` Travis Rhoden
2012-11-08 15:08 ` Travis Rhoden
2012-11-08 17:36 ` Travis Rhoden
2012-11-08 17:41 ` 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=509B6C2E.2050708@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=trhoden@gmail.com \
--cc=wido@widodh.nl \
/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