CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "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: Thu, 14 Jun 2012 14:04:54 +0200	[thread overview]
Message-ID: <4FD9D366.3060305@profihost.ag> (raw)
In-Reply-To: <4FD9D187.8030601@profihost.ag>

I got this fixed by deleting all content in /srv/osd.X. But now i get 
with the next branch this one:

=== osd.32 ===
pushing conf and monmap to ssdstor002:/tmp/mkfs.ceph.4885
2012-06-14 14:02:09.333309 7f815cd26780 -1 journal FileJournal::_open: 
unable to open journal: open() failed: (2) No such file or directory
2012-06-14 14:02:09.690097 7f815cd26780 -1 filestore(/srv/osd.32) could 
not find 23c2fcde/osd_superblock/0//-1 in index: (2) No such file or 
directory
2012-06-14 14:02:09.758456 7f815cd26780 -1 created object store 
/srv/osd.32 journal /journal/osd.32.journal for osd.32 fsid 
308b2ada-5c2a-4b54-b094-b7035413d247
creating private key for osd.32 keyring /etc/ceph/osd.32.keyring
creating /etc/ceph/osd.32.keyring
collecting osd.32 key

Stefan

  reply	other threads:[~2012-06-14 12:05 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 [this message]
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

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=4FD9D366.3060305@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    /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