List, 
We are currently  trying to build a cluster using OCFS2 on ia64.
The one point we are stuck seems to be on loading the configfs.ko
module.
Our platform is :
RHEL4 AS - U2 kernel  2.6.9-22.EL #1 SMP
We have downloaded the modules from oss.oracle.com:
ocfs2-2.6.9-22.0.1.EL-1.0.9-1.ia64.rpm
ocfs2console-1.0.3-1.ia64.rpm
ocfs2-tools-1.0.3-1.ia64.rpm
Installation via rpm went fine:
[root at linux2 ocfs2-rpms]# rpm -Uvh \
ocfs2-2.6.9-22.0.1.EL-1.0.9-1.ia64.rpm \ ocfs2console-1.0.3-1.ia64.rpm \
ocfs2-tools-1.0.3-1.ia64.rpm 
Preparing...                ###########################################
[100%]
   1:ocfs2-tools            ###########################################
[ 33%]
   2:ocfs2-2.6.9-22.0.1.EL  ###########################################
[ 67%]
   3:ocfs2console           ###########################################
[100%]
The ocfs console also starts nicely.
Problem is with cluster -> configure => nodes:
Console complains:
"could not start cluster stack. This must be resolved before any OCFS2
filesystem can be mounted"
From the FAQ, the cluster stack can be started using
/etc/rc.d/init.d/o2cb, And the FAQ indicates that it should first be
configured.
We tried that (with and without a config file present in :
/etc/ocfs2/cluster.conf), And in all cases, the o2cb command fails on
the load-stage:
[root at linux2 init.d]# ./o2cb configure
Configuring the O2CB driver.
This will configure the on-boot properties of the O2CB driver.
The following questions will determine whether the driver is loaded on
boot.  The current values will be shown in brackets ('[]').  Hitting
<ENTER> without typing an answer will keep that current value.  Ctrl-C
will abort.
Load O2CB driver on boot (y/n) [y]: y
Cluster to start on boot (Enter "none" to clear) [clu1]:
Writing O2CB configuration: OK
Loading module "configfs": Unable to load module "configfs"
Failed
We tried several other option to the o2cb : load and start.
And all fail with the same message :
Loading module "configfs": Unable to load module "configfs"
Question :
 - what can cause this error ?
 - how can we fix, or even investigate this error ?
Regards,
Yuri van Buren & Piet de Visser
Yuri.van.buren - at - logicacmg.com
Piet.de.visser - at - logicacmg.com
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential information
and/or be subject to legal privilege. It should not be copied, disclosed to,
retained or used by, any other party. If you are not an intended recipient then
please promptly delete this e-mail and any attachment and all copies and inform
the sender. Thank you.