From: Lalit Bhasin <lkb@one.com>
To: cpwu@tnsoft.com.cn
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Error while creating ceph cluster
Date: Fri, 03 Jun 2011 12:30:29 +0530 [thread overview]
Message-ID: <1307084429.3791.2.camel@lb> (raw)
In-Reply-To: <1307016212.13031.15.camel@lb>
On Thu, 2011-06-02 at 17:33 +0530, Lalit Bhasin wrote:
> On Thu, 2011-06-02 at 15:55 +0000, Jeff Wu wrote:
> > Hi ,
> >
> > Could you create the folder
> > node0: /data/osd0/osd0 /data/osd0/osd1
> > node1: /data/osd1/osd0 /data/osd1/osd1
> >
> > or
> > try to modify " osd data = /data" at your ceph.conf,
> > then create /data/osd0 and /data/osd1 at your node0&&node1.
> >
> > I had filed the issue at :
> >
> > http://tracker.newdream.net/issues/1015
> >
> >
> > but Greg Farnum added the Comment :"
> >
> > You need to create the directory yourself and this is deliberate. It
> > prevents administrators from not fully setting up their cluster and
> > accidentally having the OSD use the root partition when they meant to
> > use a separate drive mounted at /osd."
> >
> > Jeff ,Wu
> >
> Thanks Jeff. This helped. I now used single ceph.conf file on both the
> nodes, and used $i substitution for osd and mon, and it worked ( so
> kept /data/osd1 and /data/osd0 in node1 and node0 respectively).
>
>
> Subsequently file system creation worked fine, and all ceph daemons
> started fine. But mount gives error as below:
> --
> lalitb@node0:/data/osd0$ sudo mount -t ceph 192.168.230.12:/ /ceph
> [sudo] password for lalitb:
> mount error 5 = Input/output error
> lalitb@node0:/data/osd0$
> ---
>
> Where 192.168.230.12 is IP address of node0. Cannot see any error in
> syslog.
>
> - Lalit
>
Ok, I modified ceph.conf file to create osd journal on writehead mode,
and mount was successful after this. It seems this is requirement for
non-brtfs.
- Lalit
> >
> >
> >
> >
> > On Thu, 2011-06-02 at 15:41 +0800, Lalit Bhasin wrote:
> > > On Thu, 2011-06-02 at 15:14 +0000, Jeff Wu wrote:
> > > > Hi ,
> > > > try the steps:
> > > > 1. use root user;
> > > > 2. manually create /data/osd${N} folder.
> > > Jeff, I ensured that /data/osd0 ( on node0) and /data/osd1 ( on node1)
> > > existed before shooting this command on node1. Got same error using root
> > > user also ( ofcourse this time there was no permission denied error
> > > while writing to error logs).
> > > mkcephfs is failing while trying to execute below command on node0:
> > >
> > > ssh node0 /sbin/mkcephfs -d /tmp/mkcephfs.e3FNLexFkx --init-daemon osd.0
> > >
> > > And it is reporting error as:
> > >
> > > ** ERROR: error creating empty object store in /data/osd1: error 2: No
> > > such file or directory
> > >
> > > Which is somewhat true since /data/osd1 only exists in node1, and not
> > > node0. Does it means there are some error in ceph.conf.
> > >
> > > - Lalit
> > >
> > >
> > >
> > > >
> > > > Jeff ,Wu
> > > >
> > > > On Thu, 2011-06-02 at 14:59 +0800, Lalit Bhasin wrote:
> > > > > Guys, I am new to ceph. Trying to create a 2 node cluster setup of ceph.
> > > > > Getting errors during mk file system : http://dpaste.com/hold/549518/.
> > > > > Any idea what's going wrong?
> > > > >
> > > > >
> > > > > - Lalit
> > > > >
> > > > > --
> > > > > 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
> > >
> > >
> > > --
> > > 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
> >
> > --
> > 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:[~2011-06-03 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 6:59 Error while creating ceph cluster Lalit Bhasin
2011-06-02 15:14 ` Jeff Wu
2011-06-02 7:41 ` Lalit Bhasin
2011-06-02 8:12 ` Anders Saaby
2011-06-02 15:55 ` Jeff Wu
2011-06-02 12:03 ` Lalit Bhasin
2011-06-03 7:00 ` Lalit Bhasin [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=1307084429.3791.2.camel@lb \
--to=lkb@one.com \
--cc=ceph-devel@vger.kernel.org \
--cc=cpwu@tnsoft.com.cn \
/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.