-
-
Notifications
You must be signed in to change notification settings - Fork 729
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
borg crashes when backing up to gvfs volume #8120
Comments
Your filesystem doesn't work correctly. borg does a file "open" and the fs responds with:
|
#7937 also had this issue. |
Indeed it looks very similar. However, it needs to be noted that: a) it happens only with |
You can try to reproduce this on a local filesystem to see whether it only happens on cifs. "not supported" as error response to "open()" is weird. |
Oh, and try without that "gvfs" and just do a normal cifs mount and try with that also. |
On kernel-based cifs volume EDIT: EVEN MORE EDIT: Even weirder is that the exception happens on the second attempt to open |
I played with EDIT: No, it's not at random.
consequent fail:
|
OK, so guess this is a gvfs bug? Or is borg doing something wrong or unusual? |
It looks like a gvfs bug to me, but this is just like, my opinion. I will find out. |
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
BUG
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.2.4
Operating system (distribution) and version.
Debian 12.5
Hardware / network configuration, and filesystems used.
Source: local ext4
Destination: CIFS mounted via FUSE (gvfs) with
gio mount smb://…
.How much data is handled by borg?
(The question isn't clear)
Full borg commandline that lead to the problem (leave away excludes and passwords)
borg check ::2024-W08-1
Describe the problem you're observing.
borg crashes
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
Yes, it happens every time.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: