Unable to resolve permission denied error #174
-
Describe the BugI backed up to an older version of this container for a while. I upgraded the container, but forgot to keep anything but the data (including the config volumes and run command). Now, Time Machine sees the backup and asks to reattach, but gets a permission error when attempting to back up. Expected BehaviorBack up without permission error Steps to Reproduce
How You're Launching the Container
Container Logs
Additional ContextHere are logs from TimeMachine:
Here's the permissions from the host:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Sorry that I never got around to responding. Not sure if you are still having issue or not but I'll say that debugging errors beyond the initial connection to time machine isn't my strong suit as a lot of the macos processes that run to actually do the backup are not something I am familiar with and there are many messages that look like errors but don't impact the backup process which makes it even harder to filter through logs to find the actual culprit. Unfortunately in many of these situations, it tends to be easiest to clear persistent data and start a new time machine backup. |
Beta Was this translation helpful? Give feedback.
-
Funny enough, my laptop starting getting some similar errors this morning when I was attempting to do a manual backup. Just dropping in logs for when I am able to actually do some comparisons to figure out what is actually an error. Failure on my m1 macbookThis was an incremental backup; I had just started a new time machine backup less than a week ago because the sparsebundle seemed to be corrupted.
Success in a VMI created a VM, did a 1st backup and then did another to just get a successful backup to compare to:
|
Beta Was this translation helpful? Give feedback.
-
Try setting the environment variable for |
Beta Was this translation helpful? Give feedback.
Try setting the environment variable for
SMB_VFS_OBJECTS
to:SMB_VFS_OBJECTS="fruit streams_xattr"
and see if that resolves the issue for you. It started working for me after I did that.