Continuous replication problem with multiple SR

florent

@Gheppy it's always easier to fix when we can build a minimal setup that reproduce the issue
thanks for your report

Gheppy

Hello, the problem has reappeared.
This time with a different behavior.
It hangs at this stage, and the export tasks do not even start/show.

Info:

XCP-ng 8.3 up to date,
XOCE commit fcefaaea85651c3c0bb40bfba8199dd4e963211c

olivierlambert

@Gheppy Are you sure you are on latest commit on master?

Gheppy

@olivierlambert
The problem start with this commit cbc07b319fea940cab77bc163dfd4c4d7f886776
This is ok 7994fc52c31821c2ad482471319551ee00dc1472

olivierlambert

@Gheppy It's not clear to me. Is it fixed on latest commit on master as of now?

Gheppy

@olivierlambert
I update to last commit, two more change is on git now

The problem still exists. From what I've noticed, export tasks start being created and then disappear shortly after. And then a few moments later the import tasks appear and it remains blocked like this.

Only up to this commit 7994fc52c31821c2ad482471319551ee00dc1472 (inclusive) , everything is ok.

EDIT: I read on the forum about similar problems. I don't have NBD enabled.

florent

@Gheppy is there anything in the xo ? like an error on "readblock" ?

Gheppy

@florent
I will update to the latest version and look at the logs.
Now I have version 7994fc52c31821c2ad482471319551ee00dc1472

florent

@Gheppy if this is what I think it should have been fixed by https://github.com/vatesfr/xen-orchestra/commit/3c8efb4dc3e1cb3955521063047227849cfb6ed3

0

fbeauchamp committed to vatesfr/xen-orchestra

fix(backups): non NBD backups stalls (#8766)

Gheppy

@florent
The same result
Logs, but task is blocked on importing step

{
  "data": {
    "mode": "delta",
    "reportWhen": "always"
  },
  "id": "1751375761951",
  "jobId": "109e74e9-b59f-483b-860f-8f36f5223789",
  "jobName": "tb-xxxx-xxxx-vrs7",
  "message": "backup",
  "scheduleId": "40f57bd8-2557-4cf5-8322-705ec1d811d2",
  "start": 1751375761951,
  "status": "pending",
  "infos": [
    {
      "data": {
        "vms": [
          "629bdfeb-7700-561c-74ac-e151068721c2"
        ]
      },
      "message": "vms"
    }
  ],
  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "629bdfeb-7700-561c-74ac-e151068721c2",
        "name_label": "tb-xxxx-xxxx-vrs7"
      },
      "id": "1751375768046",
      "message": "backup VM",
      "start": 1751375768046,
      "status": "pending",
      "tasks": [
        {
          "id": "1751375768586",
          "message": "snapshot",
          "start": 1751375768586,
          "status": "success",
          "end": 1751375772595,
          "result": "904c2b00-087f-45ae-9799-b6dad1680aff"
        },
        {
          "data": {
            "id": "1afcdfda-6ede-3cb5-ecbf-29dc09ea605c",
            "isFull": true,
            "name_label": "tb-vrs1-RAID",
            "type": "SR"
          },
          "id": "1751375772596",
          "message": "export",
          "start": 1751375772596,
          "status": "pending",
          "tasks": [
            {
              "id": "1751375773638",
              "message": "transfer",
              "start": 1751375773638,
              "status": "pending"
            }
          ]
        },
        {
          "data": {
            "id": "a5d2b22e-e4be-c384-9187-879aa41dd70f",
            "isFull": true,
            "name_label": "tb-vrs6-RAID",
            "type": "SR"
          },
          "id": "1751375772611",
          "message": "export",
          "start": 1751375772611,
          "status": "pending",
          "tasks": [
            {
              "id": "1751375773654",
              "message": "transfer",
              "start": 1751375773654,
              "status": "pending"
            }
          ]
        }
      ]
    }
  ]
}

florent

@Gheppy and nothing in the journalctl log ?

Gheppy

hmm,
I found the solution, after I read here on forum.
I enable this options and save and then disable and save and now is ok. Task is running again. It is running with last commit to
So the problem is with these settings which may not exist in the task created before the update.