-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Error saving lock file in v0.13 on M1 Mac using SMB backend #3720
Comments
Thanks for the report! It is another case of a file system which does not support the diff --git a/internal/backend/local/local.go b/internal/backend/local/local.go
index 0ae023b8..a92ce091 100644
--- a/internal/backend/local/local.go
+++ b/internal/backend/local/local.go
@@ -2,6 +2,7 @@ package local
import (
"context"
+ "fmt"
"hash"
"io"
"io/ioutil"
@@ -166,6 +167,9 @@ func (b *Local) Save(ctx context.Context, h restic.Handle, rd restic.RewindReade
// Ignore error if filesystem does not support fsync.
err = f.Sync()
syncNotSup := errors.Is(err, syscall.ENOTSUP)
+ if err != nil {
+ fmt.Fprintf(os.Stderr, "sync error (%T): %#v, notsupported: %v\n", err, err, syncNotSup)
+ }
if err != nil && !syncNotSup {
return errors.WithStack(err)
} |
Searching for the error in the go source code turns up |
I think the problem in the forum is unrelated as the error reports a different operation and path. |
Could you test whether #3752 fixes the problem for you? |
Output of
restic version
How did you run restic exactly?
from a script file with contents of:
What backend/server/service did you use to store the repository?
SMB
Expected behavior
Not to error out creating lock file
Actual behavior
This is the results of running the script
(note that if I watch that folder in Finder, I do see a lock file beginning with that name appear and then disappear in the locks directory)
Steps to reproduce the behavior
Run Restic with any command that requires creating a lock file
Do you have any idea what may have caused this?
Something in v0.13.0 seems to have caused this.
I get this error with both the 0.13.0 and 0.13.1 binaries, but when I run with the 0.12.1 binary it works fine.
The symptom seems to be very similar to a prior issue: #2395
Do you have an idea how to solve the issue?
Unfortunately, no. For now I've reverted back to running v0.12.1
Did restic help you today? Did it make you happy in any way?
Restic has been an awesome backup tool...but something in v13 broke it for me :(
The text was updated successfully, but these errors were encountered: