INN commit: trunk/doc/pod (cycbuff.conf.pod install.pod)
rra at isc.org
Tue Feb 16 19:47:53 UTC 2010
Date: Tuesday, February 16, 2010 @ 11:47:52
Update the size limit of block devices. It has changed since
the time our documentation was written.
Thanks to Miquel van Smoorenburg and Russ Allbery.
cycbuff.conf.pod | 14 +++++++++++---
install.pod | 14 +++-----------
2 files changed, 14 insertions(+), 14 deletions(-)
--- cycbuff.conf.pod 2010-02-15 18:53:40 UTC (rev 8985)
+++ cycbuff.conf.pod 2010-02-16 19:47:52 UTC (rev 8986)
@@ -147,10 +147,18 @@
Use block devices directly. If your operating system allows you to call
mmap() on block devices (Solaris and recent versions of Linux do, FreeBSD
at last report does not), this is the recommended method since you can
-avoid all of the native file system overhead. Note, however, that each
-cycbuff cannot be larger than S<2 GB> with this method, so if you need a lot
-of spool space, you may have to go back to disk files.
+avoid all of the native file system overhead.
+Note that some OSes do not support files larger than S<2 GB>, which will
+limit the size you can make a single cycbuff, but you can still combine
+many cycbuffs into each metacycbuff. Very old versions of Linux (before 2.4
+kernels, that raised the limit to S<2 TB>) are known to have this limitation;
+FreeBSD does not. Some OSes that support large files don't support direct
+access to block devices for large partitions (Solaris prior to S<Solaris
+7>, or not running in 64-bit mode, is in this category); on those OSes,
+if you want cycbuffs over S<2 GB>, you'll have to use regular files.
+If in doubt, keep your cycbuffs smaller than S<2 GB>.
Partition the disk to make each partition equal to or smaller than S<2 GB>.
If you're using Solaris, set up your partitions to avoid the first
cylinder of the disk (or otherwise the cycbuff header will overwrite the
--- install.pod 2010-02-15 18:53:40 UTC (rev 8985)
+++ install.pod 2010-02-16 19:47:52 UTC (rev 8986)
@@ -1067,17 +1067,9 @@
For each metacycbuff, you now need to determine how many cycbuffs will
make up the metacycbuff, the size of those cycbuffs, and where they will
-be stored. Some OSes do not support files larger than S<2 GB>, which will
-limit the size you can make a single cycbuff, but you can still combine
-many cycbuffs into each metacycbuff. Older versions of Linux are known to
-have this limitation; FreeBSD does not. Some OSes that support large
-files don't support direct access to block devices for large partitions
-(Solaris prior to S<Solaris 7>, or not running in 64-bit mode, is in this
-category); on those OSes, if you want cycbuffs over S<2 GB>, you'll have to
-use regular files. If in doubt, keep your cycbuffs smaller than S<2 GB>.
-Also, when laying out your cycbuffs, you will want to try to arrange them
-across as many physical disks as possible (or use a striped disk array and
-put them all on that).
+be stored. Also, when laying out your cycbuffs, you will want to try to
+arrange them across as many physical disks as possible (or use a striped
+disk array and put them all on that).
In order to use any cycbuff larger than S<2 GB>, you need to build INN with
the B<--enable-largefiles> option. See L<Installing INN> for more
More information about the inn-committers