-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
recover breaks when custom properties appear as nodes #123
Comments
I have yet to get into the shell (it is still assigning and linking entries) but this could help. Some files don't have any contents BUT attributes, so writing attributes to a file that doesn't exist, won't work. So, this monkey-patch works around that. Long term, it should be considered if those empty files are to be touched too, causing them to have empty contents instead ( diff --git a/recuperabit/logic.py b/recuperabit/logic.py
index a0b2411..776e1d6 100644
--- a/recuperabit/logic.py
+++ b/recuperabit/logic.py
@@ -259,7 +259,10 @@ def recursive_restore(node, part, outputdir, make_dirs=True):
if mtime is not None:
atime = time.mktime(atime.astimezone().timetuple())
mtime = time.mktime(mtime.astimezone().timetuple())
- os.utime(restore_path, (atime, mtime))
+ try:
+ os.utime(restore_path, (atime, mtime))
+ except:
+ logging.error(u"Could not set timestamps (utime, atime) on %s", restore_path)
if is_directory:
for child in node.children: |
Hello!
One of our customers has experienced a massive data crash due to a blackout. While restoring (
restore 2 5
), the following error appears:Those are custom props. Can I skip them, somehow?
This is from a HyperV VHDX mounted on a Debian VM.
Thanks!
The text was updated successfully, but these errors were encountered: