Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2022-01-10 Thread Bernhard Turmann
Hello Val, hello Ard, I am not sure, but the issue might be fixed. There is an interesting comment in the upstream changelog [1] of Ceph Pacific v16.2.5: A long-standing bug that prevented 32-bit and 64-bit client/server interoperability under msgr v2 has been fixed. In particular, mixing armv7l

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2022-01-10 Thread Bernhard Turmann
Hello Val, hello Ard, I am not sure, but the issue might be fixed. There is an interesting comment in the upstream changelog [1] of Ceph Pacific v16.2.5: A long-standing bug that prevented 32-bit and 64-bit client/server interoperability under msgr v2 has been

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2020-06-18 Thread Bernd Zeimetz
Hi Ard, On 6/18/20 1:28 PM, Ard van Breemen wrote: >> The biggest issue in maintaining ceph is to make it build on 32 bit >> architectures. This seems not to be supported at all by upstream anymore. > > First of all, I don't know what your goal is to support 32 bit. Debian supports it, so it sho

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2020-06-18 Thread Ard van Breemen
Hi Bernd On 2020-05-27 21:22, Bernd Zeimetz wrote: sorry for not replying inline, but I thought I'd just share my general opinion on this. The biggest issue in maintaining ceph is to make it build on 32 bit architectures. This seems not to be supported at all by upstream anymore. First of all

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2020-05-27 Thread Bernd Zeimetz
Hi, sorry for not replying inline, but I thought I'd just share my general opinion on this. The biggest issue in maintaining ceph is to make it build on 32 bit architectures. This seems not to be supported at all by upstream anymore. Between 14.2.7 and 14.2.9 I had a longer look into the issue a

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2020-05-27 Thread Ard van Breemen
Hi, On Tue, May 26, 2020 at 06:35:20PM +0200, Val Lorentz wrote: > Thanks for the tip. > > I just tried downgrading an OSD (armhf) and a monitor (amd64) to > 14.2.7-1~bpo10+1 using http://snapshot.debian.org/ ; but they are still > unable to communicate ("failed decoding of frame header: > buffer

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2020-05-26 Thread Val Lorentz
Thanks for the tip. I just tried downgrading an OSD (armhf) and a monitor (amd64) to 14.2.7-1~bpo10+1 using http://snapshot.debian.org/ ; but they are still unable to communicate ("failed decoding of frame header: buffer::bad_alloc"). So this might be a different issue, although related.

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2020-05-26 Thread Ard van Breemen
Hi Guys, I've had working OSD's on armhf using 14.2.7 fixed using the workaround from #956293. The OSD and mon worked on armhf 14.2.7 and amd64 14.2.8 (proxmox install). When I upgraded the 14.2.7 cluster to 14.2.9, everything still worked, until I rebooted the proxmox server. Everything sinc

Bug#961481: ceph: Protocol incompatibility between armhf and amd64

2020-05-24 Thread Val Lorentz
Package: ceph Version: 14.2.9-1~bpo10+1 Dear maintainers, I run a cluster made of armhf and amd64 OSDs, and amd64 monitors and manager. I recently updated my cluster from Luminous (12, in buster) to Nautilus (14, in buster-backports), following the instructions here: https://docs.ceph.com/docs/m