From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph next branch: error creating empty object store in /srv/osd.10: (22) Invalid argument
Date: Fri, 15 Jun 2012 07:50:30 +0200 [thread overview]
Message-ID: <4FDACD26.4030803@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206141315390.23137@cobra.newdream.net>
Am 14.06.2012 22:17, schrieb Sage Weil:
> On Thu, 14 Jun 2012, Stefan Priebe - Profihost AG wrote:
> Is it possible that the osd journal you configured is a file in the osd
> data directory that doesn't already exist
Sure is this wrong?
[osd]
osd journal = /journal/osd.$id.journal
osd journal size = 1000
and the /journal dir is empty.
>, and you didn't specify the 'osd
> journal size' option in ceph.conf?
no it is - see above
> The change here is that ceph-osd --mkfs no longer wipes out previous data,
> so that's now your job.
ah OK ;-) didn't know that.
> But it only creates the journal file when the
> size is specified, otherwise it needs to already be present...
It wasn't present but the size was set. Strangely the error occours but
it still creates the file... ?!
Stefan
next prev parent reply other threads:[~2012-06-15 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 11:56 ceph next branch: error creating empty object store in /srv/osd.10: (22) Invalid argument Stefan Priebe - Profihost AG
2012-06-14 12:04 ` Stefan Priebe - Profihost AG
2012-06-14 20:17 ` Sage Weil
2012-06-15 5:50 ` Stefan Priebe - Profihost AG [this message]
2012-06-15 16:29 ` Sage Weil
2012-06-15 20:58 ` Stefan Priebe
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=4FDACD26.4030803@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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.