View Single Post
Posts: 539 | Thanked: 165 times | Joined on Feb 2010 @ Berlin, Germany
#239
Originally Posted by debernardis View Post
Robbie, though my opt filesystem after the last backup was left in an inconsistent state, after reinstalling the Nov 1st images through your version 0.32, I could subsequently restore the today's backup tar files, both for rootfs and optfs, with the older version (0.50-something) I had in the Nov 1st backup.

Sorry if this seems confusing: basically the issue is that even if backupmenu damaged the opt filesystem, today's backups were still good, but they couldn't be restored in the borked optfs until it was reset through the img reinstall.
I had this issue too (stale nfs handles in optfs) back in late september and there was no way in restoring anything useful. I defintely was not backup-menu's fault as I didn't run it the day the fs broke. I could do a backup afterwards using plain tar command as root and tar was complaining about these broken files as they could not be read but the backup finished. Therefore you should have a close look at your (tar-)backup as it might be it's not complete!
In the end what you did was: overwriting the whole partition using the image-backup (all fs-errors are eliminated) and then overwriting those files that tar could read and save when using the tar-backup. All files not read are therefore as old as your image-backup.
As my optfs was completely messed up I lost a lot of data which was not backed up by hildon-backup. Handling with the images I backed up was also no option as the latest one was way too old.
 

The Following User Says Thank You to x-lette For This Useful Post: