Continuous replication fails every time

julien-f

Could this be related to this: https://github.com/vatesfr/xen-orchestra/issues/4640?

BluejacketScott created this issue in vatesfr/xen-orchestra

closed XO From source restore backup fails with VDI_IO_ERROR #4640

txsastre

@rizaemet-0 could you tell me how have you reverted to 5.50.1 ? thanks

rizaemet 0

@txsastre I'm taking snapshot of XO vm before every update. Simple revent it.

Because it is from source so I have no support subscription. I recommend this to you.

txsastre

@rizaemet-0 thanks you've got the right. I already doing this, but I didn't know if you uninstalled it and installed a previous version.

it was just curiosity. So I'm gonna rollback to a previous snapshot too.

Thank you

Danp

@txsastre I outlined the procedure here --

https://xcp-ng.org/forum/post/18974

txsastre

@Danp thanks ! but I have rolled back to a previous version ( 5.50.1) and now I'm testing the backup again.

Fungusware

Can any comment on the fact that all of these issues are caused because 'import_raw_vdi' doesn't support Chunked transfers?

This used to be fine casuse the loophole that allowed a massive Content-Length has been closed.

(here: xapi-project/vhd-tool@f978789#diff-a1476b2332c40710d3f1791146a29aeaL484 ).

Regards.

0

jonludlam committed to xapi-project/vhd-tool

XSI-19 locate VHD footer based on file size

I order to locate the footer in a VHD file or stream, the total length
of that file or stream must be known. This commit passes it when it is
known. This depends on a corresponding change in the ocaml-vhd library.

Signed-off-by: Christian Lindig <christian.lindig@citrix.com>

RKENS

I saw this note relating to ZFS: It is not yet possible to import, migrate or export a VDI to/from a ZFS SR

Could that be why my continuous replication is failing? I'm trying to replicate from one ZFS SR to another on a different server.

olivierlambert

No, since few release, ZFS should support all operations.

RKENS

That's too bad. I don't see where anyone really had any solution.

olivierlambert

Your CR issue might be related to a XO bug on master, not too a XCP-ng issue