[Ocfs2-tools-commits] mfasheh commits r1179 - trunk/mkfs.ocfs2

[svn-commits@oss.oracle.com]

Author: mfasheh
Signed-off-by: smushran
Date: 2006-04-21 13:26:34 -0500 (Fri, 21 Apr 2006)
New Revision: 1179

Modified:
   trunk/mkfs.ocfs2/mkfs.ocfs2.8.in
Log:
Update the mkfs.ocfs2 man page to reflect the new -T option.

Signed-off-by: smushran



Modified: trunk/mkfs.ocfs2/mkfs.ocfs2.8.in
===================================================================
--- trunk/mkfs.ocfs2/mkfs.ocfs2.8.in	2006-04-18 22:45:05 UTC (rev 1178)
+++ trunk/mkfs.ocfs2/mkfs.ocfs2.8.in	2006-04-21 18:26:34 UTC (rev 1179)
@@ -2,7 +2,7 @@
 .SH "NAME"
 mkfs.ocfs2 \- Creates an \fIOCFS2\fR file system.
 .SH "SYNOPSIS"
-\fBmkfs.ocfs2\fR [ \fB\-b\fR \fIblock\-size\fR ] [ \fB\-C\fR \fIcluster\-size\fR ] [ \fB\-L\fR \fIvolume\-label\fR ] [ \fB\-N\fR \fInumber\-of\-nodes\fR ] [ \fB\-J\fR \fIjournal\-options\fR ] [ \fB\-F\fR ] [ \fB\-q\fR ] [ \fB\-v\fR ] [ \fB\-V\fR ] \fIdevice\fR [ \fIblocks-count\fI ]
+\fBmkfs.ocfs2\fR [ \fB\-b\fR \fIblock\-size\fR ] [ \fB\-C\fR \fIcluster\-size\fR ] [ \fB\-L\fR \fIvolume\-label\fR ] [ \fB\-N\fR \fInumber\-of\-nodes\fR ] [ \fB\-J\fR \fIjournal\-options\fR ] [ \fB\-T\fR \fIfilesystem\-type\fR ] [ \fB\-F\fR ] [ \fB\-q\fR ] [ \fB\-v\fR ] [ \fB\-V\fR ] \fIdevice\fR [ \fIblocks-count\fI ]
 .SH "DESCRIPTION"
 .PP 
 \fBmkfs.ocfs2\fR is used to create an \fIOCFS2\fR file system on a \fIdevice\fR, 
@@ -14,16 +14,19 @@
 .SH "OPTIONS"
 .TP
 \fB\-b\fR \fIblock\-size\fR
-Valid block size values are 512, 1K, 2K and 4K bytes per block. If omitted,
-a value will be hueristically determined by the file system size.  A block size
-of 512 bytes is never recommended. Choose 1K, 2K or 4K.
+Valid block size values are 512, 1K, 2K and 4K bytes per block. If
+omitted, a value will be hueristically determined based on the
+expected usage of the file system (see the \fB\-T\fR option). A block
+size of 512 bytes is never recommended. Choose 1K, 2K or 4K.
 
 .TP
 \fB\-C\fR \fIcluster\-size\fR
-Valid cluster size values are 4K, 8K, 16K, 32K, 64K, 128K, 256K,
-512K and 1M. If omitted, a value will be hueristically determined by the
-file system size. For volumes expected to store large files, like database files,
-a \fIcluster\-size\fR of 128K or more is recommended. For others, 16K\-64K.
+Valid cluster size values are 4K, 8K, 16K, 32K, 64K, 128K, 256K, 512K
+and 1M. If omitted, a value will be hueristically determined based on
+the expected usage of the file system (see the \fB\-T\fR option). For
+volumes expected to store large files, like database files, a
+\fIcluster\-size\fR of 128K or more is recommended. For others,
+16K\-64K.
 
 .TP
 \fIblocks-count\fR
@@ -56,6 +59,25 @@
 .RE
 
 .TP
+\fB\-T\fR \fIfilesystem\-type\fR 
+Specify how the filesystem is going to be used, so that mkfs.ocfs2 can
+chose optimal filesystem parameters for that use. The supported
+filesystem types are:
+.RS 1.2i
+.TP
+\fBmail\fR
+Appropriate for file systems which will have many meta data
+updates. Creates a larger journal.
+.RE
+.RS 1.2i
+.TP
+\fBdatafiles\fR
+Appropriate for file systems which will host a relatively small number
+of very large files. A small journal is selected. Cluster size will be
+at least 128K.
+.RE
+
+.TP
 \fB\-F\fR
 For existing \fIOCFS2\fR volumes, \fImkfs.ocfs2\fR ensures the volume
 is not mounted on any node in the cluster before formatting. For that to