From: Mark Nelson <mark.nelson@inktank.com>
To: Travis Rhoden <trhoden@gmail.com>
Cc: 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 11:41:02 -0600 [thread overview]
Message-ID: <509BEEAE.3000805@inktank.com> (raw)
In-Reply-To: <CACkq2mqkFEeivwRnrKURkfTiMFjq0jqN8ED8A+BxdJoQaBG1DQ@mail.gmail.com>
On 11/08/2012 11:36 AM, Travis Rhoden wrote:
> Solved!
>
> I stumbled into the solution while switching from block device to a
> file. I was being bit by running mkcephfs multiple times -- it wasn't
> really failing on the journal, it was failing because the OSD data
> disk had been initialized before. I couldn't see that until I used a
> file for the journal and then I see log output like:
Yeah, that was a change that landed a couple of months ago. It's really
important now to blow away the old data (I just reformat) if you want a
totally clean ceph deployment rather than just running mkcephfs.
>
> === osd.0 ===
> 2012-11-08 16:41:37.677620 7ffc3cfcd780 -1 provided osd id 0 != superblock's -1
> 2012-11-08 16:41:37.678726 7ffc3cfcd780 -1 ** ERROR: error creating
> empty object store in /var/lib/ceph/osd/ceph-0: (22) Invalid argument
>
> I unmounted the OSD's that had been touched before, reformatted them,
> and then remounted. I setup ceph.conf to use block devices for the
> journals, and then everything proceeded normally.
>
> So the final relevant bits from my ceph.conf file look like:
>
> [osd]
> osd journal size = 0
> journal dio = true
> journal aio = true
>
> [osd.0]
> host = ceph1
> osd journal = /dev/sda5
>
> [osd.1]
> host = ceph1
> osd journal = /dev/sda6
> ...
>
> Thanks,
>
> - Travis
>
> On Thu, Nov 8, 2012 at 10:08 AM, Travis Rhoden <trhoden@gmail.com> wrote:
>> One more thing -- Google search says this is harmless -- I see quite a
>> few of these in syslog:
>>
>> hdparm: sending ioctl 2285 to a partition!
> --
> 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
>
prev parent reply other threads:[~2012-11-08 17:40 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
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 [this message]
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=509BEEAE.3000805@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=trhoden@gmail.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.