From: Jeff Wu <cpwu@tnsoft.com.cn>
To: Sage Weil <sage@newdream.net>
Cc: Gregory Farnum <gregf@hq.newdream.net>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Andrew Lv <mllv@tnsoft.com.cn>
Subject: Re: Performence test on ceph v0.23 + EXT4 and Btrfs
Date: Thu, 2 Dec 2010 15:31:48 +0800 [thread overview]
Message-ID: <1291275108.1757.90.camel@cephhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1012012209140.606@cobra.newdream.net>
在 2010-12-02四的 14:10 +0800,Sage Weil写道:
> On Thu, 2 Dec 2010, Jeff Wu wrote:
> > ÿÿ 2010-12-02ÿÿÿÿ 10:35 +0800ÿÿGregory Farnumÿÿÿÿÿÿ
> > > On Wed, Dec 1, 2010 at 5:38 PM, Jeff Wu <cpwu@tnsoft.com.cn> wrote:
> > > >> > and i also detect a issue ,take the following steps:
> > > >> >
> > > >> > $. mckephfs -c ceph.conf -v --mkbtrfs -a
> > > >> > $ init-ceph - ceph.conf --btrfs -v -a start
> > > >> > then execute:
> > > >> > $ init-ceph - ceph.conf --btrfs -v -a stop
> > > >> >
> > > >> > this command can't stop OSD0 and OSD1 cosd process:
> > > >> > OSD0:
> > > >> > /usr/local/bin/cosd -i 0 -c ceph.conf
> > > >> > OSD1:
> > > >> > /usr/local/bin/cosd -i 1 -c ceph.conf
> > > >> Not sure I understand what you're doing here. Also, it looks like
> > > >> you've got a malformed command there -- you don't specify the "-c"
> > > >> option, just the nonexistent "-" option. ;)
> > > >
> > > > Oh,Sorry, i mean that , if i don't create folder "/var/run/ceph" at OSD
> > > > hosts manually. Execute the command : "$init-ceph -c ceph.conf --btrfs
> > > > -v -a stop " ,which can't auto-kill OSD host cosd process, like this :
> > > > OSD0 host:
> > > > $ ps -ef | grep cosd
> > > > root 13987 1 0 Dec01 ? 00:02:55 /usr/local/bin/cosd -i 0
> > > > -c ceph.conf
> > > > OSD1 host:
> > > > $ ps -ef | grep cosd
> > > > root 14028 1 0 Dec01 ? 00:02:53 /usr/local/bin/cosd -i 1
> > > > -c ceph.conf
> > > >
> > > > I have to execute "kill -9 13987 " and "kill -9 14028" to kill cosd
> > > > process manually, or ,next time , it will fail to execute "$ init-ceph
> > > > -c ceph.conf --btrfs -v -a start " command.
> > > Ah. I think that /var/run/ceph is where init-ceph stores the PIDs. It
> > > ought to be created automatically; if it's not we should fix that.
> > > What version of Ceph are you running, and where from? I'd imagine it's
> > > being packaged wrong or something.
> >
> > Hi ,
> > i download ceph 0.23 from
> > http://ceph.newdream.net/download/ceph-0.23.tar.gz
> >
> > So , maybe , should i add
> > "
> > [global]
> > pid file = /var/run/ceph/$name.pid
>
> That's the default, so no... I think the problem is that 'make install'
> does 'mkdir -p /var/run/ceph'. The .deb and .rpm create the dir, but an
> install from source does not. There is probably a similar problem with
> the osd class tmp dir.
>
Yes, when i try to use RBD , need also create "/var/lib/ceph/tmp"
mamually. I install ceph server with ceph-0.23.tar.gz.
Jeff,wu
> sage
--
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:[~2010-12-02 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291001135.1872.106.camel@cephhost>
[not found] ` <1291001398.1872.107.camel@cephhost>
[not found] ` <1291001962.1872.113.camel@cephhost>
[not found] ` <1291002250.1872.116.camel@cephhost>
2010-11-29 3:53 ` Performence test on ceph v0.23 + EXT4 and Btrfs Jeff Wu
2010-11-29 17:07 ` Gregory Farnum
2010-11-30 2:55 ` Jeff Wu
2010-11-30 3:18 ` Gregory Farnum
2010-11-30 6:19 ` Jeff Wu
2010-11-30 17:07 ` Gregory Farnum
2010-12-01 1:35 ` Jeff Wu
2010-12-01 6:59 ` Jeff Wu
2010-12-01 16:05 ` Gregory Farnum
2010-12-02 1:38 ` Jeff Wu
2010-12-02 2:35 ` Gregory Farnum
2010-12-02 3:22 ` Jeff Wu
2010-12-02 6:10 ` Sage Weil
2010-12-02 7:31 ` Jeff Wu [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=1291275108.1757.90.camel@cephhost \
--to=cpwu@tnsoft.com.cn \
--cc=ceph-devel@vger.kernel.org \
--cc=gregf@hq.newdream.net \
--cc=mllv@tnsoft.com.cn \
--cc=sage@newdream.net \
/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