ENAMETOOLONG in orchestra.log during merge

Anonabhar

Hi All,

After upgrading my XO from sources, I am seeing a lot of these errors in the /var/log/orchestra.log

Are these something to worry about? Just concerned that I am storing corrupted backups at this point.

2022-02-03T21:42:02.699Z xo:backups:mergeWorker INFO merging /xo-vm-backups/360d038b-1ed2-fabf-86af-61b5147fa3c0/vdis/c1f16ecc-6233-4843-8d43-20e503880cdd/9d7d0f22-e6c7-4841-870b-a5029f8f5e51/20220126T193321Z.vhd: 269/269
2022-02-03T21:42:04.208Z xo:backups:mergeWorker FATAL ENAMETOOLONG: name too long, rename '/run/xo-server/mounts/41561065-7ed0-4956-8b9f-33d29d72d7e0/xo-vm-backups/.queue/clean-vm/_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________20211108T200210Z' -> '/run/xo-server/mounts/41561065-7ed0-4956-8b9f-33d29d72d7e0/xo-vm-backups/.queue/clean-vm/________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________20211108T200210Z' {
  error: [Error: ENAMETOOLONG: name too long, rename '/run/xo-server/mounts/41561065-7ed0-4956-8b9f-33d29d72d7e0/xo-vm-backups/.queue/clean-vm/_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________20211108T200210Z' -> '/run/xo-server/mounts/41561065-7ed0-4956-8b9f-33d29d72d7e0/xo-vm-backups/.queue/clean-vm/________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________20211108T200210Z'] {
    errno: -36,
    code: 'ENAMETOOLONG',
    syscall: 'rename',
    path: '/run/xo-server/mounts/41561065-7ed0-4956-8b9f-33d29d72d7e0/xo-vm-backups/.queue/clean-vm/_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________20211108T200210Z',
    dest: '/run/xo-server/mounts/41561065-7ed0-4956-8b9f-33d29d72d7e0/xo-vm-backups/.queue/clean-vm/________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________20211108T200210Z'
  }
}

EDIT: Sorry.. I forgot to add that I am using commit: 15d06, x-server 5.87.0 and xo-web 5.92.0
Thanks,
~Peg

olivierlambert

Ping @julien-f

julien-f

@anonabhar Hi, this is a known issue that happens after a task has failed too many time, what's important is the initial error that left us in this state. It should be (possibly far) above from this log.

There is nothing much XO can do to handle this task apart from deleting this file to avoid this error, in the meantime, you can delete it manually.

Anonabhar

@julien-f Hi Julien

Oh ok.. I think I understand now. It looks like the UUID inside of the ____files don't exist and must have been some leftovers from the previous or failed merges in the past. Some of them are 9+ months old... Is it safe to just delete these files or is there any way to tell XO to delete the files if they have no corresponding UUID (like a auto-cleanup?)

julien-f

@anonabhar You can safely delete these files