filelevel restore with XFS and LVM

[henri9813]

Hello,

I try to restore file using file level restore.

My VM has an XFS filesystem over LVM.

Here is the log of the Xen-orchestra container:

xen-orchestra  | 2024-03-03T15:28:56.873Z xo:api WARN henri@devigne.digital | backupNg.listFiles(...) [38ms] =!> Error: Command failed: vgchange -ay rl
xen-orchestra  | File descriptor 19 (/var/lib/xo-server/data/leveldb/LOG) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 22 (/var/lib/xo-server/data/leveldb/LOCK) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 25 (/dev/fuse) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 26 (/var/lib/xo-server/data/leveldb/000049.log) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 29 (/var/lib/xo-server/data/leveldb/MANIFEST-000047) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  | File descriptor 112 (/dev/urandom) leaked on vgchange invocation. Parent PID 54: /usr/local/bin/node
xen-orchestra  |   WARNING: VG name rl is used by VGs s12ubK-c4u7-T0Vx-1gnd-WRmN-AHRg-SGOI7F and CyQDuF-5Lk1-cCA3-c0Tb-hd3f-qPl6-JAbFfk.
xen-orchestra  |   Fix duplicate VG names with vgrename uuid, a device filter, or system IDs.
xen-orchestra  |   Multiple VGs found with the same name: skipping rl
xen-orchestra  |   Use --select vg_uuid=<uuid> in place of the VG name.

Do you know why I have theses errors ?

Best regards

[ronivay]

Hey,

I've seen some issues with LVM file restore in the past on XO, i'd suggest checking their forum for similar cases.

The error in this case suggests that the VG name where you're trying to restore from might be conflicting with a VG on your host where the container is running.

[henri9813]

Oh you right, then, that's a beautiful limitation because my host is a vm ( like the other one ) and come from the same installation process, so, same VG ^^'

[ronivay]

Yeah that's slightly annoying but makes sense as XO has to mount the disk to be able to fetch anything from it. As this cannot be done inside the container, anything on the host will have the potential to conflict.

[henri9813]

I will try to create a new VM for my XO without LVM etc... .

I come back to share the results :)

[henri9813]

Hello,

I deploy a fresh xo without lvm, now, I have this error:

mount: /tmp/wh2o7uxhqzq: unknown filesystem type 'LVM2_member'.

But it seems related to vatesfr/xen-orchestra#7029

[fbeauchamp]

this is an issue on XO side, discovering LVM is tricky and improvment are on our roadmap