From 089224975b25f9086143f40b6153e24d75587fd3 Mon Sep 17 00:00:00 2001 From: Marian Beermann Date: Fri, 2 Jun 2017 13:12:43 +0200 Subject: [PATCH] docs: quotas: clarify compatbility; only relevant to serve side also cf. "Enforcing the quota": The quota is enforcible only if *all* :ref:`borg_serve` versions accessible to clients support quotas --- docs/internals/data-structures.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/internals/data-structures.rst b/docs/internals/data-structures.rst index e7fbb4963..d7c70ce03 100644 --- a/docs/internals/data-structures.rst +++ b/docs/internals/data-structures.rst @@ -233,8 +233,11 @@ state). .. rubric:: Compatibility with older servers and enabling quota after-the-fact If no quota data is stored in the hints file, Borg assumes zero quota is used. -Thus, if a repository with an enabled quota is written to with an older version -that does not understand quotas, then the quota usage will be erased. +Thus, if a repository with an enabled quota is written to with an older ``borg serve`` +version that does not understand quotas, then the quota usage will be erased. + +The client version is irrelevant to the storage quota and has no part in it. +The form of error messages due to exceeding quota varies with client versions. A similar situation arises when upgrading from a Borg release that did not have quotas. Borg will start tracking quota use from the time of the upgrade, starting at zero.