When this last occurred for me, it happened after the backup was complete, or at least after the backup had been running for a while. I'm unsure if it was during, before or after the 'verification' phase.
Just now, when running the command you posted, the error did not occur. I haven't had this error anyways for quite some time since I've been using the workaround of having an rbind mount, but just now I re-did the symlink which caused the error before, and the error did not occur. I'm now using deja-dup 34.2 in Gentoo, and when it originally occurred I was using an earlier version of deja-dup in Ubuntu. I'm not sure if it's completely fixed for me, if my different setup can no longer reproduce the error, or if it just worked this one time, so if anyone else who had experienced in the past could test with deja-dup 34.2, that would probably be best. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1217959 Title: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup" Status in Déjà Dup: Incomplete Status in duplicity package in Ubuntu: Incomplete Bug description: Linux release: Ubuntu 13.04 64bit Kernel: 3.8.0-29-generic Python: 2.7.4 Deja Dup: 26.0 Duplicity: 0.6.21 Hi. I've tried to do my monthly or so backup recently, but Deja Dup crashed after trying to backup a very large file (VM disk with Windows 7, 50GB or so). I tried to do another one, this time excluding all my large VM's. However, now when trying to do a backup I'm getting the following error a few seconds after inputting my encryption password: Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found in backup I've tried reinstalling both deja-dup and duplicity, purging duplicity, deleting deja-dup and duplicity from /home/tom/.cache, deleting the backup files on the external drive, deleting it's config as described here http://askubuntu.com/questions/53980/how-to-delete- all-the-settings-for-deja-dup. I know (well, I have some evidence supporting this) that the drive itself isn't faulty as I managed to backup my old laptop to the drive using duplicity and it worked fine (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs momentarily. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
