[ceph-users] Re: rbd map: corrupt full osdmap (-22) when

2023-05-05 Thread Kamil Madac
Ilya, Thanks for clarification. On Thu, May 4, 2023 at 1:12 PM Ilya Dryomov wrote: > On Thu, May 4, 2023 at 11:27 AM Kamil Madac wrote: > > > > Thanks for the info. > > > > As a solution we used rbd-nbd which works fine without any issues. If we > will have time we will also try to disable ipv4

[ceph-users] Re: rbd map: corrupt full osdmap (-22) when

2023-05-04 Thread Ilya Dryomov
On Thu, May 4, 2023 at 11:27 AM Kamil Madac wrote: > > Thanks for the info. > > As a solution we used rbd-nbd which works fine without any issues. If we will > have time we will also try to disable ipv4 on the cluster and will try kernel > rbd mapping again. Are there any disadvantages when usin

[ceph-users] Re: rbd map: corrupt full osdmap (-22) when

2023-05-04 Thread Kamil Madac
Thanks for the info. As a solution we used rbd-nbd which works fine without any issues. If we will have time we will also try to disable ipv4 on the cluster and will try kernel rbd mapping again. Are there any disadvantages when using NBD instead of kernel driver? Thanks On Wed, May 3, 2023 at 4

[ceph-users] Re: rbd map: corrupt full osdmap (-22) when

2023-05-03 Thread Ilya Dryomov
On Wed, May 3, 2023 at 11:24 AM Kamil Madac wrote: > > Hi, > > We deployed pacific cluster 16.2.12 with cephadm. We experience following > error during rbd map: > > [Wed May 3 08:59:11 2023] libceph: mon2 (1)[2a00:da8:ffef:1433::]:6789 > session established > [Wed May 3 08:59:11 2023] libceph: a

[ceph-users] Re: rbd map: corrupt full osdmap (-22) when

2023-05-03 Thread Eugen Block
Hi, seems like a reoccuring issue, e.g. [1] [2], but it seems to be triggered by something different than [1] since you don't seem to have discontinuing OSD numbers. Maybe a regression, I don't really know, maybe file a new tracker issue for that? Thanks, Eugen [1] https://tracker.ceph.c