-
-
Notifications
You must be signed in to change notification settings - Fork 756
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
setting storage_quota to 0 (unlimited) cli doesnt work #8499
Comments
Yeah, looks like there is a bug there. That check for less than 10M was added late because people forgot the "M" and set their repos to unpractically low quota (assuming that borg defaults to some big unit if no unit is given). Guess it was overlooked that 0 is a useful value for disabling the quota. |
BTW,
|
|
The "problem" is that when using a borg repo via ssh, the repository code is executed LOCALLY on the server. Also, considering that borg2 will work very differently anyway, I don't think there will be any "new features" in |
We don't want to accept very small quota limits < 10M, but 0 (quota disabled) is acceptable.
config: fix acceptance of storage_quota 0, fixes #8499
fixed in 1.4-maint, master branch does not have |
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes.
Is this a BUG / ISSUE report or a QUESTION?
Bug + Docs issue.
System information. For client/server mode post info for both machines.
Your borg version (borg -V).
borg 1.2.8
Operating system (distribution) and version.
Platform: Linux t480.l 6.10.11+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.10.11-1~bpo12+1 (2024-10-03) x86_64
Describe the problem you're observing.
The docs say:
but running
borg config . storage_quota 0
gives me:
When i do
borg config . storage_quota -d
thenborg config . -l
showsWhich is not the default of 0 and possibly has unknown implications later on.
The text was updated successfully, but these errors were encountered: