-
-
Notifications
You must be signed in to change notification settings - Fork 741
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 init: add a --additional-free-space=X option? default? #6288
Comments
Did you try |
About a default |
I tried As I understand it the size of |
Right, only local But I think there's also some temporary free space needed for repo index, hints, etc - and the size of these depend on the size of the repo. Also, there could be outside influence on the free space if there is other stuff running on the borg repo server (so even if borg lets some space free / checks for free space according to additional_free_space, that could go away any time). |
i had a quick look and yes, i think an option |
and even without that, we could also change the repo config default value for additional_free_space to a non-zero value. |
Maybe ask if not given and suggest 2G with some hints or a pointer to the docs? And |
@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 providers like borgbase.com with relatively small (10GB) "for free" accounts. Do you have an idea how we can raise the default without impacting such an offer too much? |
Hmm, guess whether that would make a difference for services like borgbase.com depends on whether they are using the borg-based quota ( |
We use both, file system quotas and Borg quotas. The latter don't work on append-only repos, I think. We also set |
Keeping 2GB available by default may be too much, since users can set the quota for a repo as low as 1 GB. |
Hmm, difficult to come up with a good value for everybody. |
See also #5313. |
On a remote backup the disk quota was reached and borg failed to connect because
borg serve
just dies and locally I get:Connection closed by remote host. Is borg working on the server?
I couldn't find a way to get it working again, so I ended up having to delete the full backup and loose all history.
I found the
storage_quota
andadditional_free_space
options, but no way to set them on an existing backup except by manually using sftp. It seems only--storage-quota
is exposed via theinit
command, but not the other option (which from what I read seems more useful).Locally I have borg 1.1.17, not sure what version Hetzner has on its storage boxes/backup spaces.
Shouldn't
additional_free_space
be set by default to prevent unrecoverable errors like this?The text was updated successfully, but these errors were encountered: