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]

 



Hi,

In the meantime I did some further test. I've created a new erasure coded
datapool 'ecpool_test' and if I create a new rbd image with this data pool
I can create snapshots, but I can't create snapshots on both new and
existing images with existing data pool 'ecpool_hdd'

just one thought, could this be a caps mismatch? Is it the same user in those two pools who creates snaps (or tries to)? If those are different users could you share the auth caps?

Zitat von Reto Gysi <rlgysi@xxxxxxxxx>:

That was all that it logged.
In the meantime I did some further test. I've created a new erasure coded
datapool 'ecpool_test' and if I create a new rbd image with this data pool
I can create snapshots, but I can't create snapshots on both new and
existing images with existing data pool 'ecpool_hdd'

#create new image on existing erasure code data-pool ecpool_hdd
root@zephir:~# rbd create -p rbd --data-pool ecpool_hdd test_ecpool_hdd
--size 10G

#create new image on new erasure code data-pool ecpool_test
root@zephir:~# rbd create -p rbd --data-pool ecpool_test test_ecpool_test
--size 10G

# trying to create snap-shot of image with data pool ecpool_hdd -> fails
root@zephir:~# rbd snap create test_ecpool_hdd@backup --debug-ms 1
--debug-rbd 20
2023-04-17T21:52:43.623+0200 7f3f787174c0  1  Processor -- start
2023-04-17T21:52:43.623+0200 7f3f787174c0  1 --  start start
2023-04-17T21:52:43.623+0200 7f3f787174c0  1 --2-  >> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x562a3dd350c0
0x562a3dd35490 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-17T21:52:43.623+0200 7f3f787174c0  1 --2-  >> [v2:
192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x562a3dd359d0
0x562a3dd42730 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-17T21:52:43.623+0200 7f3f787174c0  1 --2-  >> [v2:
192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x562a3dd42c70
0x562a3dd45050 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-17T21:52:43.623+0200 7f3f787174c0  1 --  --> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] -- mon_getmap magic: 0 v1 --
0x562a3dc24b70 con 0x562a3dd350c0
2023-04-17T21:52:43.623+0200 7f3f787174c0  1 --  --> [v2:
192.168.1.10:3300/0,v1:192.168.1.10:6789/0] -- mon_getmap magic: 0 v1 --
0x562a3dc1e1b0 con 0x562a3dd359d0
2023-04-17T21:52:43.623+0200 7f3f787174c0  1 --  --> [v2:
192.168.43.208:3300/0,v1:192.168.43.208:6789/0] -- mon_getmap magic: 0 v1
-- 0x562a3dbba680 con 0x562a3dd42c70
2023-04-17T21:52:43.623+0200 7f3f7668d700  1 --2-  >> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x562a3dd350c0
0x562a3dd35490 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-17T21:52:43.623+0200 7f3f7668d700  1 --2-  >> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x562a3dd350c0
0x562a3dd35490 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:43298/0 (socket says 192.168.1.1:43298)
2023-04-17T21:52:43.623+0200 7f3f7668d700  1 -- 192.168.1.1:0/3758799544
learned_addr learned my addr 192.168.1.1:0/3758799544 (peer_addr_for_me v2:
192.168.1.1:0/0)
2023-04-17T21:52:43.623+0200 7f3f75e8c700  1 --2- 192.168.1.1:0/3758799544
[v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x562a3dd359d0
0x562a3dd42730 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-17T21:52:43.623+0200 7f3f7668d700  1 -- 192.168.1.1:0/3758799544 >>
[v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x562a3dd42c70
msgr2=0x562a3dd45050 unknown :-1 s=STATE_CONNECTING_RE l=0).mark_down
2023-04-17T21:52:43.623+0200 7f3f7668d700  1 --2- 192.168.1.1:0/3758799544
[v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x562a3dd42c70
0x562a3dd45050 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-17T21:52:43.623+0200 7f3f7668d700  1 -- 192.168.1.1:0/3758799544 >>
[v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x562a3dd359d0
msgr2=0x562a3dd42730 unknown :-1 s=STATE_CONNECTION_ESTABLISHED
l=0).mark_down
2023-04-17T21:52:43.623+0200 7f3f7668d700  1 --2- 192.168.1.1:0/3758799544
[v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x562a3dd359d0
0x562a3dd42730 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-17T21:52:43.623+0200 7f3f7668d700  1 -- 192.168.1.1:0/3758799544
--> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] --
mon_subscribe({config=0+,monmap=0+}) v3 -- 0x562a3dbd1d60 con
0x562a3dd350c0
2023-04-17T21:52:43.623+0200 7f3f7668d700  1 --2- 192.168.1.1:0/3758799544
[v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x562a3dd350c0
0x562a3dd35490 secure :-1 s=READY pgs=511 cs=0 l=1 rev1=1 crypto
rx=0x7f3f6800a700 tx=0x7f3f68005b10 comp rx=0 tx=
0).ready entity=mon.0 client_cookie=b20073a6af526567 server_cookie=0
in_seq=0 out_seq=0
2023-04-17T21:52:43.623+0200 7f3f7568b700  1 -- 192.168.1.1:0/3758799544
<== mon.0 v2:192.168.1.1:3300/0 1 ==== mon_map magic: 0 v1 ==== 467+0+0
(secure 0 0 0) 0x7f3f680089b0 con 0x562a3dd350c0
2023-04-17T21:52:43.623+0200 7f3f7568b700  1 -- 192.168.1.1:0/3758799544
<== mon.0 v2:192.168.1.1:3300/0 2 ==== config(39 keys) v1 ==== 1461+0+0
(secure 0 0 0) 0x7f3f68008b10 con 0x562a3dd350c0
2023-04-17T21:52:43.623+0200 7f3f7568b700  1 -- 192.168.1.1:0/3758799544
<== mon.0 v2:192.168.1.1:3300/0 3 ==== mon_map magic: 0 v1 ==== 467+0+0
(secure 0 0 0) 0x7f3f68011e60 con 0x562a3dd350c0
Creating snap: 10% complete...failed.
rbd: failed to create snapshot: (95) Operation not supported
root@zephir:~#

# trying to create snapshot of image with new data pool ecpool_test ->
success
root@zephir:~# rbd snap create test_ecpool_test@backup --debug-ms 1
--debug-rbd 20
2023-04-17T21:52:52.883+0200 7f3d15ceb4c0  1  Processor -- start
2023-04-17T21:52:52.883+0200 7f3d15ceb4c0  1 --  start start
2023-04-17T21:52:52.883+0200 7f3d15ceb4c0  1 --2-  >> [v2:
192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x5603e9c7e530
0x5603e9c7e900 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-17T21:52:52.883+0200 7f3d15ceb4c0  1 --2-  >> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5603e9c785c0
0x5603e9c789f0 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-17T21:52:52.883+0200 7f3d15ceb4c0  1 --2-  >> [v2:
192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5603e9c78f30
0x5603e9c852f0 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-17T21:52:52.883+0200 7f3d15ceb4c0  1 --  --> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] -- mon_getmap magic: 0 v1 --
0x5603e9b64b70 con 0x5603e9c785c0
2023-04-17T21:52:52.883+0200 7f3d15ceb4c0  1 --  --> [v2:
192.168.1.10:3300/0,v1:192.168.1.10:6789/0] -- mon_getmap magic: 0 v1 --
0x5603e9b5e1b0 con 0x5603e9c78f30
2023-04-17T21:52:52.883+0200 7f3d15ceb4c0  1 --  --> [v2:
192.168.43.208:3300/0,v1:192.168.43.208:6789/0] -- mon_getmap magic: 0 v1
-- 0x5603e9afa680 con 0x5603e9c7e530
2023-04-17T21:52:52.883+0200 7f3d0bfff700  1 --2-  >> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5603e9c785c0
0x5603e9c789f0 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-17T21:52:52.883+0200 7f3d0bfff700  1 --2-  >> [v2:
192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5603e9c785c0
0x5603e9c789f0 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:41638/0 (socket says 192.168.1.1:41638)
2023-04-17T21:52:52.883+0200 7f3d0bfff700  1 -- 192.168.1.1:0/2685923383
learned_addr learned my addr 192.168.1.1:0/2685923383 (peer_addr_for_me v2:
192.168.1.1:0/0)
2023-04-17T21:52:52.883+0200 7f3d14825700  1 --2- 192.168.1.1:0/2685923383
[v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5603e9c78f30
0x5603e9c852f0 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-17T21:52:52.883+0200 7f3d0bfff700  1 -- 192.168.1.1:0/2685923383 >>
[v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x5603e9c7e530
msgr2=0x5603e9c7e900 unknown :-1 s=STATE_CONNECTING_RE l=0).mark_down
2023-04-17T21:52:52.883+0200 7f3d0bfff700  1 --2- 192.168.1.1:0/2685923383
[v2:192.168.43.208:3300/0,v1:192.168.43.208:6789/0] conn(0x5603e9c7e530
0x5603e9c7e900 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-17T21:52:52.883+0200 7f3d0bfff700  1 -- 192.168.1.1:0/2685923383 >>
[v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5603e9c78f30
msgr2=0x5603e9c852f0 unknown :-1 s=STATE_CONNECTION_ESTABLISHED
l=0).mark_down
2023-04-17T21:52:52.883+0200 7f3d0bfff700  1 --2- 192.168.1.1:0/2685923383
[v2:192.168.1.10:3300/0,v1:192.168.1.10:6789/0] conn(0x5603e9c78f30
0x5603e9c852f0 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-17T21:52:52.883+0200 7f3d0bfff700  1 -- 192.168.1.1:0/2685923383
--> [v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] --
mon_subscribe({config=0+,monmap=0+}) v3 -- 0x5603e9b11d60 con
0x5603e9c785c0
2023-04-17T21:52:52.883+0200 7f3d0bfff700  1 --2- 192.168.1.1:0/2685923383
[v2:192.168.1.1:3300/0,v1:192.168.1.1:6789/0] conn(0x5603e9c785c0
0x5603e9c789f0 secure :-1 s=READY pgs=513 cs=0 l=1 rev1=1 crypto
rx=0x7f3cfc00a700 tx=0x7f3cfc005b10 comp rx=0 tx=
0).ready entity=mon.0 client_cookie=d9d113e873a32a9f server_cookie=0
in_seq=0 out_seq=0
2023-04-17T21:52:52.883+0200 7f3d13823700  1 -- 192.168.1.1:0/2685923383
<== mon.0 v2:192.168.1.1:3300/0 1 ==== mon_map magic: 0 v1 ==== 467+0+0
(secure 0 0 0) 0x7f3cfc008a30 con 0x5603e9c785c0
2023-04-17T21:52:52.883+0200 7f3d13823700  1 -- 192.168.1.1:0/2685923383
<== mon.0 v2:192.168.1.1:3300/0 2 ==== config(39 keys) v1 ==== 1461+0+0
(secure 0 0 0) 0x7f3cfc008b90 con 0x5603e9c785c0
2023-04-17T21:52:52.883+0200 7f3d13823700  1 -- 192.168.1.1:0/2685923383
<== mon.0 v2:192.168.1.1:3300/0 3 ==== mon_map magic: 0 v1 ==== 467+0+0
(secure 0 0 0) 0x7f3cfc0063a0 con 0x5603e9c785c0
Creating snap: 100% complete...done.
root@zephir:~#


root@zephir:~# ceph osd pool ls detail | egrep "ecpool_hdd|ecpool_test"

pool 37 'ecpool_hdd' erasure profile 3-2-jerasure size 5 min_size 4
crush_rule 5 object_hash rjenkins pg_num 128 pgp_num 128 autoscale_mode on
last_change 72385 lfor 0/0/65311 flags
hashpspool,ec_overwrites,selfmanaged_snaps stripe_width 12288
compression_algorithm lz4 compression_mode aggressive
compression_required_ratio 0.875 application cephfs,rbd
pool 87 'ecpool_test' erasure profile 3-2-jerasure size 5 min_size 4
crush_rule 9 object_hash rjenkins pg_num 1 pgp_num 1 autoscale_mode on
last_change 72720 flags hashpspool,ec_overwrites,selfmanaged_snaps
stripe_width 12288 compression_algorithm lz4 compression_mode aggressive
compression_required_ratio 0.825 application cephfs,rbd
root@zephir:~#

root@zephir:~# rbd config pool list ecpool_hdd > ecpool_hdd.txt
root@zephir:~# rbd config pool list ecpool_test > ecpool_test.txt
root@zephir:~# diff ecpool_hdd.txt ecpool_test.txt
root@zephir:~#

I'm currently running
ceph osd pool repair ecpool_hdd
and will check later if that fixes the problem

Cheers

Reto



Am Mo., 17. Apr. 2023 um 21:18 Uhr schrieb Ilya Dryomov <idryomov@xxxxxxxxx
:

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


_______________________________________________
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