Is there really a need to have configfs as a module? I could see that it might have been needed before when OCFS2 wasn't part of the linux tree. When I configure my linux kernels, I tend to build monolithic kernels. This means I have already selected and have built in configfs as well as OCFS2. Seems that the attempt to load configfs on init should be done only after it is verified the running kernel doesn't already have configfs up and running. -- Steven <critch@basesys.com>
Ah yes... you want o2cb service script to be smarter. :)
Edit /etc/init.d/o2cb and remove load_module configfs from the following
line.
It wouldn't make it smarter... just would get it to work.
LOAD_ACTIONS=("load_module configfs"
"mount_fs configfs "'$(configfs_path)'
"load_module ocfs2_nodemanager"
"load_module ocfs2_dlm"
"load_module ocfs2_dlmfs"
"mount_fs ocfs2_dlmfs /dlm")
Log a bug in oss.oracle.com/bugzilla so that we remember to fix this.
Steven wrote:> Is there really a need to have configfs as a module? I could see that it
> might have been needed before when OCFS2 wasn't part of the linux tree.
>
> When I configure my linux kernels, I tend to build monolithic kernels.
> This means I have already selected and have built in configfs as well as
> OCFS2. Seems that the attempt to load configfs on init should be done
> only after it is verified the running kernel doesn't already have
> configfs up and running.
>