Re: Usage of rbd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 28, 2010 at 5:32 PM, ml ml <takada_ml@xxxxxxxxxxxxxxxxx> wrote:
> Hi
>
> I also trying to use rbd in my environment, following the wiki's instruction.
> and I did "ceph class activate rbd 1.2", but still not works.
>
>
>
> My situation:
>
> # mkcephfs -c /usr/local/etc/ceph/ceph.conf --allhosts --mkbtrfs
> # /etc/init.d/ceph -c /usr/local/etc/ceph/ceph.conf --allhosts start
> # cclass -a
> # ceph class activate rbd 1.2
> (snip)
> 10.09.29_09:01:30.047510 mon <- [class,activate,rbd,1.2]
> (snip)
> 10.09.29_09:01:31.067373 mon0 -> 'updated' (0)
>
> # ceph class list
> (snip)
> mon <- [class,list]
> 192.168.101.41:0/2359 --> mon0 192.168.101.41:6789/0 --
> mon_command(class list v 0) v1 -- ?+0 0x1d4ce30
> 192.168.101.41:0/2359 <== mon0 192.168.101.41:6789/0 4 ====
> mon_command_ack([class,list]=0 installed classes:
> rbd (v1.2 [x86-64]) [active]
>  v3) v1 ==== 96+0+0 (1704564143 0 0) 0x7f0268000bf0
> 10.09.29_09:01:44.151874 mon0 -> 'installed classes:
> rbd (v1.2 [x86-64]) [active]
> ' (0)
>
>
> -* looks like OK. create new pool named "testpool", and make
> -* new image named "testdata" in it.
>
>
> # rados lspools
> (snip)
> data
> metadata
> casdata
> rbd
>
> # rados mkpool testpool
> (snip)
> successfully created pool testpool
>
>
> # rbd -p testpool create testdata --size 128
> :/2428 messenger.start
> :/2428 --> mon0 192.168.101.41:6789/0 -- auth(proto 0 30 bytes) v1 --
> ?+0 0x25cfe10
> 192.168.101.41:0/2428 learned my addr 192.168.101.41:0/2428
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 1 ====
> auth_reply(proto 1 0 Success) v1 ==== 24+0+0 (1462504351 0 0)
> 0x7ff88c000940
> 192.168.101.41:0/2428 --> mon0 192.168.101.41:6789/0 --
> mon_subscribe({monmap=0+}) v1 -- ?+0 0x25d57d0
> 192.168.101.41:0/2428 --> mon0 192.168.101.41:6789/0 --
> mon_subscribe({monmap=0+,osdmap=0}) v1 -- ?+0 0x25d59b0
> 192.168.101.41:0/2428 --> mon0 192.168.101.41:6789/0 --
> mon_subscribe({monmap=0+,osdmap=0}) v1 -- ?+0 0x25d4180
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 2 ==== mon_map v1
> ==== 191+0+0 (3527398169 0 0) 0x7ff88c000c40
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 3 ====
> mon_subscribe_ack(300s) v1 ==== 20+0+0 (388814775 0 0) 0x7ff88c000920
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 4 ==== mon_map v1
> ==== 191+0+0 (3527398169 0 0) 0x7ff88c000bf0
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 5 ====
> osd_map(5,5) v1 ==== 1153+0+0 (1530501066 0 0) 0x7ff88c000920
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 6 ====
> mon_subscribe_ack(300s) v1 ==== 20+0+0 (388814775 0 0) 0x7ff88c000920
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 7 ==== mon_map v1
> ==== 191+0+0 (3527398169 0 0) 0x7ff88c000bf0
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 8 ====
> osd_map(5,5) v1 ==== 1153+0+0 (1530501066 0 0) 0x7ff88c000920
> 192.168.101.41:0/2428 --> osd0 192.168.101.41:6801/2231 --
> osd_op(client4104.0:1 testdata.rbd [stat 0~0] 4.49b3) v1 -- ?+0
> 0x25d43c0
> 192.168.101.41:0/2428 <== mon0 192.168.101.41:6789/0 9 ====
> mon_subscribe_ack(300s) v1 ==== 20+0+0 (388814775 0 0) 0x7ff88c0011e0
> 192.168.101.41:0/2428 <== osd0 192.168.101.41:6801/2231 1 ====
> osd_op_reply(1 testdata.rbd [stat 0~0] = -2 (No such file or
> directory)) v1 ==== 98+0+0 (1237653720 0 0) 0x7ff87c000990
> 192.168.101.41:0/2428 --> osd0 192.168.101.41:6801/2231 --
> osd_op(client4104.0:2 rbd_info [write 0~0] 4.573a) v1 -- ?+0 0x25d43c0
> 192.168.101.41:0/2428 <== osd0 192.168.101.41:6801/2231 2 ====
> osd_op_reply(2 rbd_info [write 0~0] = 0) v1 ==== 94+0+0 (3894334133 0
> 0) 0x7ff87c000990
> 192.168.101.41:0/2428 --> osd0 192.168.101.41:6801/2231 --
> osd_op(client4104.0:3 rbd_info [call rbd.assign_bid] 4.573a) v1 -- ?+0
> 0x25d43a0

This last operation never returns. What version are you using? Can you
add the corresponding osd logs?
Also, can you verify that /var/lib/ceph/tmp exists and is writable by
the user running the cosd daemon, and make sure that there is no
execution restriction there (this path can be configured by the 'osd
class tmp' config variable).

Thanks,
Yehuda
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux