Can't restore individual files

apassler

now i did a frech installation on a fresh debian 10 and got the same results. i installed xo with the following command:
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash

olivierlambert

Try to check if you have the issue with XOA on stable and/or latest branch.

jmm

Hi olivier,
I have same problem.
What do you mean by stable branch.
In xo_install.sh it seems to be the master branch.
On https://github.com/vatesfr/xen-orchestra I can't find any stable or latest branch
Is there another repository were I can find xen-orchestra sources ?

Thanks

olivierlambert

In XOA, there's two release channel: stable and latest. It's only in XOA. There's no hidden repository, XOA is a choice of specific commits for each parts to offer the best perfs/stability of Xen Orchestra (this work is done by a big QA pass before a new XOA update)

edit: also I have no idea where did you find this xo_install.sh, it's likely a 3rd party script, not something from us.

jmm

Thanks for the reply
Sorry but I need to be sure that we are talking about the same thing.
I am talking about building from sources.
If I follow the instructions provided here https://xen-orchestra.com/docs/from_the_sources.html
I can find : git clone -b master http://github.com/vatesfr/xen-orchestra
It seems to mean that we clone master branch
Should I replace master with stable or latest ?

olivierlambert

I wasn't talking about the build from the sources, I was asking about XOA behavior, which seems to work in both channels.
There's no branch other than master for the sources.

If you are using XO for production, I would strongly suggest to switch to XOA (to also get remote support and the updater).

Otherwise, on the sources, you might rebuild it from a commit that works for you. @julien-f will be back Monday and he'll take a look.

jmm

@olivierlambert thank's

borzel

@jmm you can also build from a tag to get a consitsent state

olivierlambert

@borzel said in Can't restore individual files:

@jmm you can also build from a tag to get a consitsent state

Not really, we do our QA on various npm packages that can be at different versions (eg a plugin with an older version, on xo-server with a more recent one). Being on master is the best solution, because we use "feature branches" to avoid breaking everything (but bug still could appear indeed)

jmm

Hi @julien-f did you find something ?

olivierlambert

We'll have a release next week based on a more recent commits, so if there is any issues on XO code, our QA will spot it

olivierlambert

So after a discussion with our devs, the change you told us in the commit was already embed in latest release of XOA, and it works.

Also we tested locally, it works even on an Ubuntu 18.04. So we can't reproduce.

Please try to delete/reinstall your XO or try to find a way to reproduce it easily for everyone.

jmm

@olivierlambert ok thanks

jmm

Hi @olivierlambert
Same problem with new ubuntu 18.04.3 LTS install.
Trying do do a file restore on a delta backup of a 2019 rds server, syslog shows :
Aug 28 06:14:27 xo2 ntfs-3g[15942]: Version 2017.3.23 integrated FUSE 28
Aug 28 06:14:27 xo2 ntfs-3g[15942]: Mounted /dev/loop2 (Read-Only, label "Données", NTFS 3.1)
Aug 28 06:14:27 xo2 ntfs-3g[15942]: Cmdline options: ro,norecovery
Aug 28 06:14:27 xo2 ntfs-3g[15942]: Mount options: no,norecovery,allow_other,nonempty,relatime,fsname=/dev/loop2,blkdev,blksize=4096
Aug 28 06:14:27 xo2 ntfs-3g[15942]: Ownership and permissions disabled, configuration type 7
Aug 28 06:14:27 xo2 ntfs-3g[15942]: Unmounting /dev/loop2 (Données)

GUI stuck :

Problem is the same with centos 7 vm

jmm

My backup storage is a local vdi attached to orchestra's vm

/dev/mapper/backup-lvol0 on /backups type ext4 (rw,relatime,data=ordered)

olivierlambert

Try on Debian maybe? We can't reproduce here

Toni

I can reproduce the error.

It happens after the following commit:
efdfa1f2f7d394078e1b80734b2724150d390d65 (chore: update dependencies on 16 Jul).

When you use the commit before it works (5bd61e3fb0378cbfe5bb7ecee3a8c910d411bfdb).

Toni

I've tested with a clean install of Debian 9 and Debian 10.
5bd61e... and before is working

From efdfa1... till today the error can be reproduced.

julien-f

@Toni I've just upgraded the dependencies again, can you tell me if it fixes the issue?

Toni

@julien-f I've tested with Debian 10 and 9.9. It doesn´t fix the issue.

Backup is mounted:
dmesg:
[23251.644870] EXT4-fs (loop0): mounted filesystem without journal. Opts: norecovery

mount:
dev/fuse on /tmp/tmp-6642wNApvzVXia4w type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/fuse on /tmp/tmp-664218x1EmTjqp2F type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0)

But you cannot select files. Only the idle symbols are shown.