From: Kern Sibbald <kern@sibbald.com>
Date: Sat, 27 May 2017 14:28:02 +0000 (+0200)
Subject: More document fixes
X-Git-Tag: Release-7.9.1
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=bc5a9e800944e81b242086f3017e297c626ef511;p=bacula%2Fdocs

More document fixes
---

diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex
index a41c19cd..ab3cda8d 100644
--- a/docs/manuals/en/main/dirdconf.tex
+++ b/docs/manuals/en/main/dirdconf.tex
@@ -2747,11 +2747,13 @@ The Pool Resource defined in the Director's configuration file
    to the Volume.  If you specify zero (the default), there is no limit
    except the physical size of the Volume.  Otherwise, when the number of
    bytes written to the Volume equals {\bf size} the Volume will be marked
-   {\bf Used}.  When the Volume is marked {\bf Used} it can no longer be
-   used for appending Jobs, much like the {\bf Full} status but it can be
+   {\bf Full}.  When the Volume is marked {\bf Full} it can no longer be
+   used for appending Jobs, but it can be
    recycled if recycling is enabled, and thus the Volume can be re-used
-   after recycling.  This value is checked and the {\bf Used} status set
-   while the job is writing to the particular volume.
+   after recycling.  The size specified is checked just before each
+   block is written to the Volume and if the Volume size would exceed the
+   specified Maximum Volume Bytes the {\bf Full} status will be set and
+   the Job will request the next available Volume to continue.
 
    This directive is particularly useful for restricting the size
    of disk volumes, and will work correctly even in the case of