TW
and even without that, we could also change the repo config default value for additional_free_space to a non-zero value. just wondering what value would fit most users / scenarios?
@m3nu I think we should have 2G .. 5G as default value there. Usually people will have hundreds of GBs local space for their backups. OTOH, there are borg storage...
Hmm, guess whether that would make a difference for services like borgbase.com depends on whether they are using the borg-based quota (`--storage-quota`) or some external mechanism.
Hmm, difficult to come up with a good value for everybody.
related: #2273
Strange error, but I'ld say file a bug against the cifs filesystem, borg only does normal filesystem operations and they should work without the filesystem going nuts. Specifically: - File...
What you could also try is using that cifs mount manually, just use some file manager and copy a bigger amount of files into it, do some renames, deletes, copies...
Fine, the jammy 1.2.0 version is from same maintainer. I just wanted to exclude any strange effects potentially coming from the pyinstaller-made fat binary (it bundles python and misc libs...
notable fs-related change between 1.1.17 and 1.2.0 i found: repository code: - `borg check` writes to repo config (to support `borg check --partial --max-duration`) - `os.statvfs(repo_path)` --> `shutil.disk_usage(repo_path)` (this is...
Maybe producing a log with `strace` could give some additional insights about where the problems begin and what was done immediately before that.