Xen Orchestra - Permissions Issue - File level restore
-
@Danp Do you have SSHFS installed?
-
One sec, Fuse not installed on debian by default... FML... repo added installing fuse.
Rebooting and then recompiling..
-
@DustinB3403 Thought you did that yesterday. Did you rebuild from scratch?
-
@Danp said in Xen Orchestra - Permissions Issue - File level restore:
@DustinB3403 Thought you did that yesterday. Did you rebuild from scratch?
No I added the universal repo yesterday for something else that was needed.
Anyways, now trying to mount a single backup I get
Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: Wed, 21 Dec 2016 19:15:18 GMT xo:api [email protected] | backup.scanDisk(...) [1s] ==> object Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: { [Error: Command failed: mount --options=loop,ro --source=/tmp/tmp-416paluKS1uHkUS/vhdi7 --target=/tmp/tmp-4160yW3G6ma9LZP Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: missing codepage or helper program, or other error Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: In some cases useful info is found in syslog - try Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: dmesg | tail or so. Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: ] Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: code: 32, Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: killed: false, Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: stdout: '', Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: stderr: 'mount: wrong fs type, bad option, bad superblock on /dev/loop0,\n missing codepage or helper program, or other error\n\n In some cases useful info is found in syslog - try\n dmesg | tail or so.\n', Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: failed: true, Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: signal: null, Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: cmd: 'mount --options=loop,ro --source=/tmp/tmp-416paluKS1uHkUS/vhdi7 --target=/tmp/tmp-4160yW3G6ma9LZP' } Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: Wed, 21 Dec 2016 19:15:18 GMT xo:api [email protected] | backup.scanFiles(...) [218ms] =!> Error: Command failed: mount --options=loop,ro --source=/tmp/tmp-416paluKS1uHkUS/vhdi7 --target=/tmp/tmp-4160yW3G6ma9LZP Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: missing codepage or helper program, or other error Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: In some cases useful info is found in syslog - try Dec 21 14:15:18 xo-test-debian-3 xo-server[416]: dmesg | tail or so.
Trying another backup . oh and dmesg | tail contains
10.867971] Adding 392188k swap on /dev/xvda5. Priority:-1 extents:1 across:392188k SSFS 13.590095] RPC: Registered named UNIX socket transport module. 13.590099] RPC: Registered udp transport module. 13.590100] RPC: Registered tcp transport module. 13.590101] RPC: Registered tcp NFSv4.1 backchannel transport module. 13.633648] FS-Cache: Loaded 13.681056] FS-Cache: Netfs 'nfs' registered for caching 13.943515] Installing knfsd (copyright (C) 1996 [email protected]). 86.204993] fuse init (API version 7.23) 86.635229] loop: module loaded
-
Seems to be specific to that backup, as I am able to restore files to my file server now without issue.
So a few things to we should try to compile into the update script, check for fuse, and install it if its not there.
-
Another is listing things like this....
398.675872] ntfs: (device loop0): ntfs_readdir(): Directory index record with vcn 0x0 is corrupt. Corrupt inode 0xe96b9. Run chkdsk. 398.675890] ntfs: (device loop0): ntfs_readdir(): Directory index record with vcn 0x0 is corrupt. Corrupt inode 0xe96b9. Run chkdsk.
So yeah.. gonna run a check disk on my VM here..
-
@DustinB3403 said in Xen Orchestra - Permissions Issue - File level restore:
Seems to be specific to that backup, as I am able to restore files to my file server now without issue.
So a few things to we should try to compile into the update script, check for fuse, and install it if its not there.
Also for libvhdi-utils
-
@Danp That was the other thing, that I installed yesterday.
libvhdi-utils
-
This would list if the packaged is installed, so how to pipe that output into the next part would be the question.
dpkg --get-selections | grep libvhdi-utils libvhdi-utils install
-
Found this code on the interweb. I would think either the 2nd or 3rd solution would work fine for our needs.
-
Yeah, this might be the easiest solution...
if [ $(dpkg-query -W -f='${Status}' nano 2>/dev/null | grep -c "ok installed") -eq 0 ]; then apt-get install nano; fi
Might need to throw up a flag or warning if the package can't be found though. Like in my case I had to add the universal repo to my debian installation before I could install libvhdi-util and fuse.
-
Should be able to check the exit code from apt-get. Now to wrap the whole thing into a nice little function that we can reuse in the future.
-
5.5.2 is out. Grab it while it's hot!
-
@Danp said in Xen Orchestra - Permissions Issue - File level restore:
5.5.2 is out. Grab it while it's hot!
Hmmm, I am glad I didn't have time to futz with the other version!
I actually don't even have XO backups set up yet. Still doing agents from inside the VMs since it works awesomely and I just haven't had time to play with XO.
-
Yeah... usually best to wait a few days for them to work out any kinks before upgrading production systems.
-
Upgraded and back to stable release.
Have you had any progress with the
wrong fs type
issue? Do you have a open issue ticket? -
@DustinB3403 No. There's an active thread over on the XO forum. I was just getting ready to post over there. Think I may have found the cause.
-
@Danp nice, post a link and I can test as well. I'm busy with another issue, so I'll have to play catch up.
-
@DustinB3403 Looks like Ubuntu has an older version of vhdimount in the repository. Can you post the output from
vhdimount -V
? -
vhdimount -V
vhdimount 20150110Copyright (C) 2012-2015, Joachim Metz.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Report bugs to [email protected].