[Ocfs2-tools-commits] smushran commits r1062 - trunk/documentation

svn-commits at oss.oracle.com svn-commits at oss.oracle.com
Fri Aug 19 16:43:36 CDT 2005 

Author: smushran
Date: 2005-08-19 16:43:34 -0500 (Fri, 19 Aug 2005)
New Revision: 1062

Modified:
   trunk/documentation/ocfs2_faq.txt
Log:
faq updated

Modified: trunk/documentation/ocfs2_faq.txt
===================================================================
--- trunk/documentation/ocfs2_faq.txt	2005-08-19 02:26:05 UTC (rev 1061)
+++ trunk/documentation/ocfs2_faq.txt	2005-08-19 21:43:34 UTC (rev 1062)
@@ -1,7 +1,7 @@
-/* -*- mode: txt; c-basic-offset: 4; -*-
- * vim: noexpandtab sw=4 ts=4 sts=0:
- */
 
+		OCFS2 - Frequently Asked Questions
+		==================================
+
 General
 -------
 
@@ -38,7 +38,7 @@
 Q04	What are the dependencies for installing ocfs2console?
 A04	ocfs2console requires e2fsprogs, glib2 2.2.3 or later, vte 0.11.10 or
 	later, pygtk2 (EL4) or python-gtk (SLES9) 1.99.16 or later,
-	python 1.99.16 or later and ocfs2-tools.
+	python 2.3 or later and ocfs2-tools.
 
 Q05	What modules are installed with the OCFS2 package?
 A05	a) configfs.ko
@@ -72,6 +72,14 @@
 	Do not forget to copy this file to all the nodes in the cluster.
 	If you ever edit this file on any node, ensure the other nodes are
 	updated as well.
+
+Q02	Should the IP interconnect be public or private?
+A02	Using a private interconnect is recommended. While OCFS2 does not
+	take much bandwidth, it does require the nodes to be alive on the
+	network and sends regular keepalive packets to ensure that they are.
+	To avoid a network delay being interpreted as a node disappearing on
+	the net leading to a STONITH, a private interconnect is recommended.
+	One could use the same interconnect for Oracle RAC and OCFS2.
 ==============================================================================
 
 O2CB Cluster Service
@@ -208,6 +216,12 @@
 	in-kernel heartbeat thread the resource to heartbeat on.
 	ocfs2_dlmfs is used by ocfs2 tools to communicate with the in-kernel
 	dlm to take and release clusterwide locks on resources.
+
+Q07	Why does it take so much time to mount the volume?
+A07	It takes around 5 secs for a volume to mount. It does so so as
+	to let the heartbeat thread stabilize. In a later release, we
+	plan to add support for a global heartbeat, which will make most
+	mounts instant.
 ==============================================================================
 
 Oracle RAC
@@ -215,7 +229,7 @@
 
 Q01	Any special flags to run Oracle RAC?
 A01	OCFS2 volumes containing the Voting diskfile (CRS), Cluster registry
-	(OCR), Data files, Redo logs, Archive logs and control files should
+	(OCR), Data files, Redo logs, Archive logs and control files must 
 	be mounted with the "datavolume" mount option. This is to ensure
 	that the Oracle processes open these files with the o_direct flag.
 
@@ -282,76 +296,27 @@
 PROC interface
 --------------
 
-Q01	How do I know what version number of the OCFS2?
+Q01	How do I know what version number?
 A01	# cat /proc/fs/ocfs2/version
 	OCFS2 1.0.0 Tue Aug  2 17:38:59 PDT 2005 (build e7bd36709a2c1cb875cf2d533a018f20)
 
-root at ca-test32:~# mounted.ocfs2 -d
-Device                FS     UUID                                  Label
-/dev/sdb1             ocfs2  e70c75a0-a08c-480a-bf50-ebda4191da30 mm_v2_dbf1
-/dev/sdb2             ocfs2  f49163e8-6288-43c4-a792-e9401fde45fa mm_v2_ctrl
-/dev/sdb3             ocfs2  2d441be2-adb6-4c52-9e19-9a7c2c485dc4 mm_v2_ocfs2
-/dev/sdb5             ocfs2  8607eae9-8e4f-4495-84e8-8db0bc9da60c mm_v2_log1
-/dev/sdb6             ocfs2  acfb7b7d-a277-4741-9791-620ea9b82670 mm_v2_log2
-/dev/sdf1             ocfs2  84749537-df45-4a97-aa28-fad63760b674 ocfs2test
-/dev/sdi2             ocfs2  5c30cc8d-ee31-414c-bc6c-a8685d738262
-/dev/sdq1             ocfs2  dca2901b-241f-406e-80e9-85dd6b452d1a oracle_home
-/dev/sdcf1            ocfs2  663764bd-1eed-4b3c-aa48-a98f0be0e574 ocfs2test
-/dev/sdcf2            ocfs2  8e2d9c21-ef47-4fea-8ac5-2306cc60455e mm_v2_log2
-/dev/sdcg1            ocfs2  663764bd-1eed-4b3c-aa48-a98f0be0e574 ocfs2test
+Q02	How do I enable and disable tracing?
+A02	To list all the debug bits along with their statuses, do:
+		# cat /proc/fs/ocfs2_nodemanager/log_mask
+	To enable tracing the bit SUPER, do:
+		# echo "SUPER allow" > /proc/fs/ocfs2_nodemanager/log_mask
+	To disable tracing the bit SUPER, do:
+		# echo "SUPER off" > /proc/fs/ocfs2_nodemanager/log_mask
+	To totally turn off tracing the SUPER bit, as in, turn off
+	tracing even if some other bit is enabled for the same, do:
+		# echo "SUPER deny" > /proc/fs/ocfs2_nodemanager/log_mask
+==============================================================================
 
+Directories
+-----------
 
-root at ca-test32:~# mounted.ocfs2 -f
-Device                FS     Nodes
-/dev/sdb1             ocfs2  ca-test91
-/dev/sdb2             ocfs2  ca-test91
-/dev/sdb3             ocfs2  ca-test91
-/dev/sdb5             ocfs2  ca-test91
-/dev/sdb6             ocfs2  ca-test91, ca-test90
-/dev/sdf1             ocfs2  Not mounted
-/dev/sdi2             ocfs2  ca-test34, ca-test35
-/dev/sdq1             ocfs2  Not mounted
-/dev/sdcf1            ocfs2  Not mounted
-/dev/sdcf2            ocfs2  Not mounted
-/dev/sdcg1            ocfs2  Not mounted
-/dev/sdcg2            ocfs2  Not mounted
-/dev/sdch1            ocfs2  ca-test30
-/dev/sdci1            ocfs2  ca-test30
-/dev/sdcj1            ocfs2  ca-test31, ca-test33, ca-test32, ca-test30
-/dev/sdcj2            ocfs2  ca-test31, ca-test33, ca-test32, ca-test30
-/dev/sdck1            ocfs2  ca-test31, ca-test33, ca-test32, ca-test30
-/dev/sdck2            ocfs2  ca-test31, ca-test33, ca-test32, ca-test30
-/dev/sdcl1            ocfs2  ca-test31, ca-test33, ca-test32, ca-test30
-/dev/sdcl2            ocfs2  ca-test31, ca-test33, ca-test32, ca-test30
-
-
-
-
-root at ca-test32:/ocfs2/archives# ocfs2cdsl  agent.ora
-root at ca-test32:/ocfs2/archives# ll
-total 8
-drwxr-xr-x  2 root root 4096 Aug  8 11:41 .
-drwxr-xr-x  5 root root 4096 Aug  8 11:41 ..
-lrwxrwxrwx  1 root root   50 Aug  8 11:41 agent.ora -> ../.cluster/hostname/{hostname}/archives/agent.ora
-
-
-
-
-
-
-root at ca-test32:/ocfs2/archives# cp /root/.bash_profile bash_profile
-root at ca-test32:/ocfs2/archives# ll
-total 9
-drwxr-xr-x  2 root root 4096 Aug  8 11:50 .
-drwxr-xr-x  5 root root 4096 Aug  8 11:41 ..
-lrwxrwxrwx  1 root root   50 Aug  8 11:41 agent.ora -> ../.cluster/hostname/{hostname}/archives/agent.ora
--rw-r--r--  1 root root  191 Aug  8 11:50 bash_profile
-root at ca-test32:/ocfs2/archives# ocfs2cdsl -c bash_profile
-root at ca-test32:/ocfs2/archives# ll
-total 8
-drwxr-xr-x  2 root root 4096 Aug  8 11:50 .
-drwxr-xr-x  5 root root 4096 Aug  8 11:41 ..
-lrwxrwxrwx  1 root root   50 Aug  8 11:41 agent.ora -> ../.cluster/hostname/{hostname}/archives/agent.ora
-lrwxrwxrwx  1 root root   53 Aug  8 11:50 bash_profile -> ../.cluster/hostname/{hostname}/archives/bash_profile
-
-
+Q01	Any limits to the number of sub-directories?
+A01	Yes. OCFS2 currently allows upto 32000 sub-directories. While this
+	limit could be increased, we will not be doing it till we
+	implement some kind of efficient name lookup (htree, etc.).
+==============================================================================

More information about the Ocfs2-tools-commits mailing list