From: Stefan Priebe <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 22:58:17 +0200 [thread overview]
Message-ID: <4FDBA1E9.50906@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206150927040.4551@cobra.newdream.net>
Am 15.06.2012 18:29, schrieb Sage Weil:
>>> 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... ?!
>
> It sure is.
>
> Can you reproduce with 'debug filestore = 20' and attach the log to this
> bug?
>
> http://tracker.newdream.net/issues/2595
done and log attached
Stefan
prev parent reply other threads:[~2012-06-15 20:58 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
2012-06-15 16:29 ` Sage Weil
2012-06-15 20:58 ` Stefan Priebe [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=4FDBA1E9.50906@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox