File Restore with backups from 1970 ?



  • I just updated to latest xo-web and xo-server from GitHub and somehow file restore seems broken to me:

    • all my backups show dates from 1970
    • selecting one of them and selecting the disk shows "no files".
    • Non file restore (delta restore) seems ok.

    Any idea?

    PS: Backups are Delta Backups and are stored on NFS if that matters.



  • Okay i already found out myself that this has been fixed in next-release branch of xo-web on GitHub 🙂
    However still show no files no matter what i enter or which vm disk i chose. Any idea?



  • Probably this.



  • I had this issue as well, @Danp and I were working to troubleshoot it. Are you using XO or XOA?

    If you are using Debian (and XO) you'll likely need a few more pieces of software to address the issue.



  • XO on ubuntu 16.04.
    Could you please be more precise about the Software needed?



  • @mhoffmann If you have ubuntu you should have all of the software needed. . . (unless minimum doesn't have the software)

    What does dpkg --get-selections | grep libvhdi-utils and dpkg --get-selections | grep fuse output?



  • Pretty sure he will be missing the one library, which can be installed with sudo apt-get install libvhdi-utils



  • Yes you are right, libvhdi-utils was indeed missing. However it still does not show up any files and most of the time not even partitions ...

    Most of the time i get these errors in syslog:

    Dec 22 09:53:57 pns-xo xo-server[812]: { [Error: Command failed: mount --options=loop,ro --source=/tmp/tmp-812HQBwW1Q2J5I2/vhdi5 --target=/tmp/tmp-8122rxqvjVEGkAo
    Dec 22 09:53:57 pns-xo xo-server[812]: mount: wrong fs type, bad option, bad superblock on /dev/loop1,
    Dec 22 09:53:57 pns-xo xo-server[812]:        missing codepage or helper program, or other error
    Dec 22 09:53:57 pns-xo xo-server[812]:        In some cases useful info is found in syslog - try
    Dec 22 09:53:57 pns-xo xo-server[812]:        dmesg | tail or so.
    

    So i guess i'm missing some other packets. Any idea which packets/drivers are necessary for XO's file restore feature???

    Is file restore supposed to be compatible to delta backups? I could imagine that this would only work with the latest full backup (synthetic full or normal full) - however would be positive surprised if it works with delta backups aswell ...



  • @mhoffmann We are seeing this issue as well. We will need to wait for further feedback from @olivierlambert or @julien-f.



  • No issues to report on XOA here (since our last update).

    It seems you are trying to mount a non-supported file system.



  • Very strange it's not working on any of our VMs. Neither windows (ntfs) VMs nor Linux VMs (mainly ubuntu with ext4).
    Any idea how to debug this?



  • Mount it manually and try to see if you got something.



  • This is the result from manual mounting --

    root@xo-5:/tmp/tmp-1103lzTnxxIlJ1kZ# mount --options=loop,ro,offset=1048576,noload --source=/tmp/tmp-1103ZFWmz5W3NlMz/vhdi6 --target=/tmp/tmp-1103lzTnxxIlJ1kZ
    mount: wrong fs type, bad option, bad superblock on /dev/loop1,
           missing codepage or helper program, or other error
    
           In some cases useful info is found in syslog - try
           dmesg | tail or so.
    

    and this is what appears in dmesg --

    [Dec22 08:46] EXT4-fs (loop1): Mount option "noload" incompatible with ext2
    

    Removing noload from the command and it appears to complete without error. However, destination directory doesn't contain anything when I checked.



  • What's your FS inside this VHD?



  • Looks like Ext4 in the one instance I checked --

    zendto@zendto:~$ sudo fdisk -l
    
    Disk /dev/xvda: 10.7 GB, 10737418240 bytes
    255 heads, 63 sectors/track, 1305 cylinders, total 20971520 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x000321ab
    
        Device Boot      Start         End      Blocks   Id  System
    /dev/xvda1            2048     2148351     1073152   82  Linux swap / Solaris
    /dev/xvda2   *     2148352    20969471     9410560   83  Linux
    
    zendto@zendto:~$ mount
    /dev/xvda2 on / type ext4 (rw,errors=remount-ro)
    
    


  • Can't reproduce here 😞



  • Also seeing on type ext2.



  • I would say it's logical on ext2 (because there is no log), but not for ext4.



  • Can you try with this branch? https://github.com/vatesfr/xo-server/pull/468



  • Still seeing some errors. Here's an example --

    Dec 22 10:18:27 xo-5 xo-server[4822]: { Error: Command failed: mount --options=loop,ro --source=/tmp/tmp-4822uHZbte7gH0or/vhdi8 --target=/tmp/tmp-4822em6i8742FWfk --types=auto
    Dec 22 10:18:27 xo-5 xo-server[4822]: mount: wrong fs type, bad option, bad superblock on /dev/loop3,
    Dec 22 10:18:27 xo-5 xo-server[4822]:        missing codepage or helper program, or other error
    Dec 22 10:18:27 xo-5 xo-server[4822]:        In some cases useful info is found in syslog - try
    Dec 22 10:18:27 xo-5 xo-server[4822]:        dmesg | tail or so.
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise.all.then.arr (/opt/xo-server/node_modules/execa/index.js:170:11)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at tryCatcher (/opt/xo-server/node_modules/bluebird/js/release/util.js:16:23)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._settlePromiseFromHandler (/opt/xo-server/node_modules/bluebird/js/release/promise.js:510:31)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._settlePromise (/opt/xo-server/node_modules/bluebird/js/release/promise.js:567:18)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._settlePromise0 (/opt/xo-server/node_modules/bluebird/js/release/promise.js:612:10)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._settlePromises (/opt/xo-server/node_modules/bluebird/js/release/promise.js:691:18)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._fulfill (/opt/xo-server/node_modules/bluebird/js/release/promise.js:636:18)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at PromiseArray._resolve (/opt/xo-server/node_modules/bluebird/js/release/promise_array.js:125:19)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at PromiseArray._promiseFulfilled (/opt/xo-server/node_modules/bluebird/js/release/promise_array.js:143:14)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._settlePromise (/opt/xo-server/node_modules/bluebird/js/release/promise.js:572:26)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._settlePromise0 (/opt/xo-server/node_modules/bluebird/js/release/promise.js:612:10)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Promise._settlePromises (/opt/xo-server/node_modules/bluebird/js/release/promise.js:691:18)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Async._drainQueue (/opt/xo-server/node_modules/bluebird/js/release/async.js:138:16)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Async._drainQueues (/opt/xo-server/node_modules/bluebird/js/release/async.js:148:10)
    Dec 22 10:18:27 xo-5 xo-server[4822]:     at Immediate.Async.drainQueues (/opt/xo-server/node_modules/bluebird/js/release/async.js:17:14)
    Dec 22 10:18:27 xo-5 xo-server[4822]:   code: 32,
    Dec 22 10:18:27 xo-5 xo-server[4822]:   killed: false,
    Dec 22 10:18:27 xo-5 xo-server[4822]:   stdout: '',
    Dec 22 10:18:27 xo-5 xo-server[4822]:   stderr: 'mount: wrong fs type, bad option, bad superblock on /dev/loop3,\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 22 10:18:27 xo-5 xo-server[4822]:   failed: true,
    Dec 22 10:18:27 xo-5 xo-server[4822]:   signal: null,
    Dec 22 10:18:27 xo-5 xo-server[4822]:   cmd: 'mount --options=loop,ro --source=/tmp/tmp-4822uHZbte7gH0or/vhdi8 --target=/tmp/tmp-4822em6i8742FWfk --types=auto' }
    Dec 22 10:18:27 xo-5 xo-server[4822]: Thu, 22 Dec 2016 16:18:27 GMT xo:api dan@checkassistflorida.com | backup.scanFiles(...) [58ms] =!> Error: Command failed: mount --options=loop,ro --source=/tmp/tmp-4822uHZbte7gH0or/vhdi8 --target=/tmp/tmp-4822em6i8742FWfk --types=auto
    Dec 22 10:18:27 xo-5 xo-server[4822]: mount: wrong fs type, bad option, bad superblock on /dev/loop3,
    Dec 22 10:18:27 xo-5 xo-server[4822]:        missing codepage or helper program, or other error
    Dec 22 10:18:27 xo-5 xo-server[4822]:        In some cases useful info is found in syslog - try
    Dec 22 10:18:27 xo-5 xo-server[4822]:        dmesg | tail or so.
    

Log in to reply