doc: limitations of addsite on different partitions

A user on the openafs-info mailing list noted that the Admin Guide is
unclear about creating read-only replicas on different partitions on
the same fileserver. Clarify the rules here.

Reviewed-on: http://gerrit.openafs.org/5745
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Reviewed-by: Derrick Brashear <shadow@dementix.org>
(cherry picked from commit c59c07132ef17589ad3466ded418c1370539b7af)

Change-Id: I68898c21e2c1aa7d6828b475dff4c1cb6d14327c
Reviewed-on: http://gerrit.openafs.org/6317
Reviewed-by: Derrick Brashear <shadow@dementix.org>
Tested-by: Derrick Brashear <shadow@dementix.org>

diff --git a/doc/xml/AdminGuide/auagd007.xml b/doc/xml/AdminGuide/auagd007.xml
index b7d84c584982d2f2128045bf9151f83c2ed23d0b..19f3196cbb4fed2752a7fa3904d9aa79710503e5 100644 (file)
--- a/doc/xml/AdminGuide/auagd007.xml
+++ b/doc/xml/AdminGuide/auagd007.xml
@@ -2083,9 +2083,14 @@
       index, rather than a full copy of the volume contents. Only if the
       read/write volume moves to another partition or changes
       substantially does the read-only volume consume significant disk
-      space. Read-only volumes kept on other partitions always consume the
-      full amount of disk space that the read/write source consumed when
-      the read-only volume was created.</para>
+      space. Read-only volumes kept on other servers' partitions always
+      consume the full amount of disk space that the read/write source
+      consumed when the read-only volume was created.</para>
+
+      <para>You cannot have a replica volume on a different partition of
+      the same server hosting the read/write volume. "Cheap" read-only
+      volumes must be on the same partition as the read/write; all other
+      read-only volumes must be on different servers.</para>
     </sect2>
 
     <sect2 id="Header_58">