DEVEL15-docs-max-part-size-20080713

LICENSE BSD
FIXES 86677

update discussion of max partition size.

(cherry picked from commit c766e74fd63a58e714d7b15ef1abfbc48b2a5a85)

diff --git a/doc/man-pages/pod1/fs_listquota.pod b/doc/man-pages/pod1/fs_listquota.pod
index eaee5820c3b56a8bd4a419a1bd9b0ce92f332304..84cc6149256a2d588a6cf968d88fbf78f949b392 100644 (file)
--- a/doc/man-pages/pod1/fs_listquota.pod
+++ b/doc/man-pages/pod1/fs_listquota.pod
@@ -30,14 +30,7 @@ To set volume quota, use the B<fs setquota> or B<fs setvol> command.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/fs_minidump.pod b/doc/man-pages/pod1/fs_minidump.pod
index 9be46e71fd9250be88f5b7d69e736cf640cf8400..be296cb8839cdd88747068f4205bffe01cd6c722 100644 (file)
--- a/doc/man-pages/pod1/fs_minidump.pod
+++ b/doc/man-pages/pod1/fs_minidump.pod
@@ -19,6 +19,16 @@ of the afsd_service.exe process.  This output can be very helpful when
 debugging the AFS Client Service when it is unresponsive to SMB/CIFS
 requests.
 
+If the AFS Client Service becomes unresponsive to any form of
+communication there may be a serious error that can only be diagnosed
+by someone with access to the source code and a debugger.  The "fs
+minidump" command can be used to force the generation of a MiniDump
+file containing the state of all of the threads in the AFS Client
+Service process.
+
+The "MiniDumpType" registry value can be used to adjust the scope of the
+process information included within the dump file.
+
 =head1 CAUTIONS
 
 This command is only available in OpenAFS for Windows version 1.4 and later.

diff --git a/doc/man-pages/pod1/fs_quota.pod b/doc/man-pages/pod1/fs_quota.pod
index d9445093b07856c77e44ef0863165d6b05a1b444..d5c6afa62ba15c74ed6c40d344580883e5ee0442 100644 (file)
--- a/doc/man-pages/pod1/fs_quota.pod
+++ b/doc/man-pages/pod1/fs_quota.pod
@@ -26,14 +26,7 @@ To set volume quota, use the B<fs setquota> or B<fs setvol> command.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/fs_setquota.pod b/doc/man-pages/pod1/fs_setquota.pod
index f0cd853a759bc935d19cd3a53fa844ddd7e03102..2a2af3e6415dfd529f853dfcdbbdccd35c3c1f1e 100644 (file)
--- a/doc/man-pages/pod1/fs_setquota.pod
+++ b/doc/man-pages/pod1/fs_setquota.pod
@@ -31,14 +31,7 @@ B<fs quota> command.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/fs_setvol.pod b/doc/man-pages/pod1/fs_setvol.pod
index 8540f7b00a6e117a35af5aa32d4252dad7ad3cc1..f09afbd3be4ef4d4bca41222c896f09e5c68814b 100644 (file)
--- a/doc/man-pages/pod1/fs_setvol.pod
+++ b/doc/man-pages/pod1/fs_setvol.pod
@@ -38,14 +38,7 @@ To set quota on one volume at a time, use the B<fs setquota> command.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/vos.pod b/doc/man-pages/pod1/vos.pod
index d09c7bf8e9234a5bd92867f05fb0cf5fe87b7d82..8d37408d8c5fd9599c2ead0baf9284703ecb771f 100644 (file)
--- a/doc/man-pages/pod1/vos.pod
+++ b/doc/man-pages/pod1/vos.pod
@@ -96,14 +96,7 @@ Commands to obtain help: B<vos apropos> and B<vos help>.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/vos_copy.pod b/doc/man-pages/pod1/vos_copy.pod
index a9cbfe6063f3c0b3a92ad45c250c0136ba233e78..6d291457fc4448074a307efe28191366423e8be2 100644 (file)
--- a/doc/man-pages/pod1/vos_copy.pod
+++ b/doc/man-pages/pod1/vos_copy.pod
@@ -27,14 +27,7 @@ the volume be stored locally by the client.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/vos_create.pod b/doc/man-pages/pod1/vos_create.pod
index 2906205637b00e302ef831526eea3777b9987eae..29ea06ae469deeecd95c0a3b3da18b1933ec6a28 100644 (file)
--- a/doc/man-pages/pod1/vos_create.pod
+++ b/doc/man-pages/pod1/vos_create.pod
@@ -62,14 +62,7 @@ mount it in the file space by using the B<fs mkmount> command.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/vos_examine.pod b/doc/man-pages/pod1/vos_examine.pod
index d1cebcae55e7ef50cc45390625961b947ea0457b..0ae5082f097d15d7e9de4cfad6598675b196ed94 100644 (file)
--- a/doc/man-pages/pod1/vos_examine.pod
+++ b/doc/man-pages/pod1/vos_examine.pod
@@ -34,14 +34,7 @@ display information from the VLDB only, use the B<vos listvldb> command.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/vos_move.pod b/doc/man-pages/pod1/vos_move.pod
index 3acb3545ab33698469aa72bf469369a748635eee..fa9233317443590d7ed2dec9e4ae5e8605e65df0 100644 (file)
--- a/doc/man-pages/pod1/vos_move.pod
+++ b/doc/man-pages/pod1/vos_move.pod
@@ -86,14 +86,7 @@ confirmation of the kill signal:
 To confirm termination of the operation, press Ctrl-C a second time; press
 any other key to continue the operation.
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod1/vos_partinfo.pod b/doc/man-pages/pod1/vos_partinfo.pod
index d3b436c456a4a01790e0be360e0b5c61bf8ee7ef..543906428d9ae9a0793bb60c3647d34251117797 100644 (file)
--- a/doc/man-pages/pod1/vos_partinfo.pod
+++ b/doc/man-pages/pod1/vos_partinfo.pod
@@ -27,14 +27,7 @@ consulted.
 
 =head1 CAUTIONS
 
-Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
-and the maximum size of a /vicepX partition on a fileserver is also 2
-terabytes. The fileserver will not report an error when it has access
-to a partition larger than 2 terabytes, but it will probably fail if
-the administrator attempts to use more than 2 terabytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2 terabytes.
+Currently, the maximum size of a volume is 2 terabytes (2^31 bytes).
 
 =head1 OPTIONS
 

diff --git a/doc/man-pages/pod8/fileserver.pod b/doc/man-pages/pod8/fileserver.pod
index 19e5f5cd73e66b454f165976184a9adc2191736c..3ab94cf8a4de61bcbd37bb0f7f5e9ee23c067b2c 100644 (file)
--- a/doc/man-pages/pod8/fileserver.pod
+++ b/doc/man-pages/pod8/fileserver.pod
@@ -232,12 +232,8 @@ option only on the relevant system type.
 
 Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
 and the maximum size of a /vicepX partition on a fileserver is 2^64 
-kilobytes. The fileserver will not report an error when it has access
-to a partition larger than 2^64 kilobytes, but it will probably fail if
-the administrator attempts to use more than 2^64 kilobytes of space. In
-addition, there are reports of erroneous disk usage numbers when
-B<vos partinfo> or other OpenAFS disk reporting tools are used with
-partitions larger than 2^64 kilobytes.
+kilobytes.  (The maximum partition size in releases 1.5.34 and earlier
+is 2^31 kilobytes.)
 
 The maximum number of directory entries is 64,000 if all of the
 entries have names that are 15 characters or less in length. A name