From: Dan Mick <dan.mick@inktank.com>
To: sheng qiu <herbert1984106@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ceph mkfs failed
Date: Thu, 07 Feb 2013 12:22:23 -0800 [thread overview]
Message-ID: <51140CFF.8000207@inktank.com> (raw)
In-Reply-To: <CAB7xdi=5q-e7FEXjrf524as4FPW-pM4z9wDrCm7boPVTr7sVLg@mail.gmail.com>
On 02/07/2013 09:59 AM, sheng qiu wrote:
> Hi,
>
> i am trying to port a local file system other than ext3,ext4,btrfs to
> manage the OSD. There are some reasons for us to do it.
> the mkcephfs stopped at this point:
>
> 2013-02-07 11:39:32.009889 7effe43d17a0 -1 filestore(/mnt/osd.0) mkfs
> failed to create leveldb: IO error:
> /mnt/osd.0/current/omap/MANIFEST-000001: Invalid argument
> 2013-02-07 11:39:32.009907 7effe43d17a0 -1 OSD::mkfs: FileStore::mkfs
> failed with error -1
> 2013-02-07 11:39:32.009949 7effe43d17a0 -1 ** ERROR: error creating
> empty object store in /mnt/osd.0: (1) Operation not permitted
Does your ssh user have permission to create dirs in /mnt?
(I'll grant you it looks like you're doing root, but, still)
> failed: 'ssh root@mon-mds /usr/local/sbin/mkcephfs -d
> /tmp/mkfs.ceph.2686 --init-daemon osd.0'
You could certainly try this command on the failing system as root,
and look with strace to see what system call is actually failing.
>
> look into the code, it failed at os/FileStore.cc --> leveldb::Status
> status = leveldb::DB::Open(options, omap_dir, &db);
>
> Does anyone have any suggestions?
>
> Thanks,
> Sheng
>
next prev parent reply other threads:[~2013-02-07 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 17:59 ceph mkfs failed sheng qiu
2013-02-07 20:22 ` Dan Mick [this message]
2013-02-07 20:42 ` sheng qiu
2013-02-07 20:53 ` Gregory Farnum
2013-02-07 22:11 ` sheng qiu
2013-02-07 22:21 ` Dan Mick
2013-02-07 22:40 ` sheng qiu
2013-02-08 16:36 ` sheng qiu
2013-02-08 17:02 ` Sage Weil
2013-02-08 17:07 ` sheng qiu
2013-02-08 17:53 ` sheng qiu
2013-02-08 20:57 ` sheng qiu
2013-02-08 21:18 ` sheng qiu
2013-02-08 21:19 ` Gregory Farnum
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=51140CFF.8000207@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=herbert1984106@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.