Re: [ceph 17.2.6] unable to create rbd snapshots for images with erasure code data-pool

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

 



On Mon, Apr 17, 2023 at 6:37 PM Reto Gysi <rlgysi@xxxxxxxxx> wrote:
>
> Hi Ilya,
>
> Thanks for the reply. Here's is the output:
>
> root@zephir:~# rbd status ceph-dev
> Watchers:
>        watcher=192.168.1.1:0/338620854 client.19264246 cookie=18446462598732840969
>
> root@zephir:~# rbd snap create ceph-dev@backup --debug-ms 1 --debug-rbd 20
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1  Processor -- start
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1 --  start start
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1 --2-  >> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5558b4e3c260 0x5558b4e3c630 unknown :-1 s=NONE pgs=0 cs=0 l=0 rev1=0 crypto rx=0 tx=0 comp rx=0 tx=0).connect
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1 --2-  >> [v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5558b4e3cc00 0x5558b4e452d0 unknown :-1 s=NONE pgs=0 cs=0 l=0 rev1=0 crypto rx=0 tx=0 comp rx=0 tx=0).connect
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1 --2-  >> [v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x5558b4e45810 0x5558b4e47bf0 unknown :-1 s=NONE pgs=0 cs=0 l=0 rev1=0 crypto rx=0 tx=0 comp rx=0 tx=0).connect
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1 --  --> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] -- mon_getmap magic: 0 v1 -- 0x5558b4d29b70 con 0x5558b4e3c260
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1 --  --> [v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] -- mon_getmap magic: 0 v1 -- 0x5558b4d231b0 con 0x5558b4e3cc00
> 2023-04-17T18:23:16.211+0200 7f5e05dca4c0  1 --  --> [v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] -- mon_getmap magic: 0 v1 -- 0x5558b4cbf680 con 0x5558b4e45810
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 --2-  >> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5558b4e3c260 0x5558b4e3c630 unknown :-1 s=BANNER_CONNECTING pgs=0 cs=0 l=0 rev1=0 crypto rx=0 tx=0 comp rx=0 tx=0)._handle_peer_banner_payload supporte
> d=3 required=0
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 --2-  >> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5558b4e3c260 0x5558b4e3c630 unknown :-1 s=HELLO_CONNECTING pgs=0 cs=0 l=0 rev1=1 crypto rx=0 tx=0 comp rx=0 tx=0).handle_hello peer v2:192.168.1.1:3300
> /0 says I am v2:192.168.1.1:42714/0 (socket says 192.168.1.1:42714)
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 -- 192.168.1.1:0/1614127865 learned_addr learned my addr 192.168.1.1:0/1614127865 (peer_addr_for_me v2:192.168.1.1:0/0)
> 2023-04-17T18:23:16.211+0200 7f5e03902700  1 --2- 192.168.1.1:0/1614127865 >> [v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5558b4e3cc00 0x5558b4e452d0 unknown :-1 s=BANNER_CONNECTING pgs=0 cs=0 l=0 rev1=0 crypto rx=0 tx=0 comp rx=0 tx=0)._handle_pe
> er_banner_payload supported=3 required=0
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 -- 192.168.1.1:0/1614127865 >> [v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x5558b4e45810 msgr2=0x5558b4e47bf0 unknown :-1 s=STATE_CONNECTING_RE l=0).mark_down
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 --2- 192.168.1.1:0/1614127865 >> [v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x5558b4e45810 0x5558b4e47bf0 unknown :-1 s=START_CONNECT pgs=0 cs=0 l=0 rev1=0 crypto rx=0 tx=0 comp rx=0 tx=0).stop
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 -- 192.168.1.1:0/1614127865 >> [v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5558b4e3cc00 msgr2=0x5558b4e452d0 unknown :-1 s=STATE_CONNECTION_ESTABLISHED l=0).mark_down
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 --2- 192.168.1.1:0/1614127865 >> [v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5558b4e3cc00 0x5558b4e452d0 unknown :-1 s=AUTH_CONNECTING pgs=0 cs=0 l=0 rev1=1 crypto rx=0 tx=0 comp rx=0 tx=0).stop
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 -- 192.168.1.1:0/1614127865 --> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] -- mon_subscribe({config=0+,monmap=0+}) v3 -- 0x5558b4cd6d60 con 0x5558b4e3c260
> 2023-04-17T18:23:16.211+0200 7f5e04103700  1 --2- 192.168.1.1:0/1614127865 >> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5558b4e3c260 0x5558b4e3c630 secure :-1 s=READY pgs=355 cs=0 l=1 rev1=1 crypto rx=0x7f5df400a700 tx=0x7f5df4005b10 comp rx=0 tx=
> 0).ready entity=mon.0 client_cookie=2d9464291c26a0e7 server_cookie=0 in_seq=0 out_seq=0
> 2023-04-17T18:23:16.211+0200 7f5e03101700  1 -- 192.168.1.1:0/1614127865 <== mon.0 v2:192.168.1.1:3300/0 1 ==== mon_map magic: 0 v1 ==== 467+0+0 (secure 0 0 0) 0x7f5df40089b0 con 0x5558b4e3c260
> 2023-04-17T18:23:16.211+0200 7f5e03101700  1 -- 192.168.1.1:0/1614127865 <== mon.0 v2:192.168.1.1:3300/0 2 ==== config(39 keys) v1 ==== 1461+0+0 (secure 0 0 0) 0x7f5df4008b10 con 0x5558b4e3c260
> 2023-04-17T18:23:16.211+0200 7f5e03101700  1 -- 192.168.1.1:0/1614127865 <== mon.0 v2:192.168.1.1:3300/0 3 ==== mon_map magic: 0 v1 ==== 467+0+0 (secure 0 0 0) 0x7f5df4011e60 con 0x5558b4e3c260
> Creating snap: 10% complete...failed.
> rbd: failed to create snapshot: (95) Operation not supported

Can you double check if this output is complete?  It looks truncated
to me -- the debug log part (lines beginning with a timestamp) should
be many times longer.

Try collecting it as follows and attach log.txt file:

$ rbd snap create ceph-dev@backup --debug-ms 1 --debug-rbd 20 >log.txt 2>&1

Thanks,

                Ilya
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux