Hi, Everything compiled correctly for the ocfs2 package, but so far the modules will not load with the "well known" module symbol error. FATAL: Error inserting ocfs2 (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown symbol in module, or unknown parameter (see dmesg) Okay not sure what is up here, any suggestions? BTW, this is the correct module location and I manually ran depmod. thanks, randy
What does dmesg say? Randy Ramsdell wrote:> Hi, > > Everything compiled correctly for the ocfs2 package, but so far the > modules will not load with the "well known" module symbol error. > > FATAL: Error inserting ocfs2 > (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown > symbol in module, or unknown parameter (see dmesg) > > > Okay not sure what is up here, any suggestions? BTW, this is the correct > module location and I manually ran depmod. > > thanks, > randy > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users@oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users >
Sunil Mushran wrote:> What does dmesg say? >I think it is suse thing, but not sure. FATAL: Error inserting ocfs2 (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown symbol in module, or unknown parameter (see dmesg) dfb02010304:/usr/src # dmesg ocfs2: disagrees about version of symbol dlm_print_one_lock ocfs2: Unknown symbol dlm_print_one_lock ocfs2: Unknown symbol o2hb_heartbeat_resource_get_by_name ocfs2: disagrees about version of symbol dlmlock ocfs2: Unknown symbol dlmlock ocfs2: disagrees about version of symbol o2nm_get_node_by_num ocfs2: Unknown symbol o2nm_get_node_by_num ocfs2: disagrees about version of symbol o2hb_setup_callback ocfs2: Unknown symbol o2hb_setup_callback ocfs2: disagrees about version of symbol dlm_unregister_domain ocfs2: Unknown symbol dlm_unregister_domain ocfs2: disagrees about version of symbol dlm_register_domain ocfs2: Unknown symbol dlm_register_domain ocfs2: disagrees about version of symbol dlm_register_eviction_cb ocfs2: Unknown symbol dlm_register_eviction_cb ocfs2: disagrees about version of symbol config_item_put ocfs2: Unknown symbol config_item_put ocfs2: disagrees about version of symbol o2net_register_handler ocfs2: Unknown symbol o2net_register_handler ocfs2: disagrees about version of symbol o2hb_register_callback ocfs2: Unknown symbol o2hb_register_callback ocfs2: disagrees about version of symbol o2hb_unregister_callback ocfs2: Unknown symbol o2hb_unregister_callback ocfs2: disagrees about version of symbol dlmunlock ocfs2: Unknown symbol dlmunlock ocfs2: disagrees about version of symbol o2nm_node_put ocfs2: Unknown symbol o2nm_node_put> Randy Ramsdell wrote: >> Hi, >> >> Everything compiled correctly for the ocfs2 package, but so far the >> modules will not load with the "well known" module symbol error. >> >> FATAL: Error inserting ocfs2 >> (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown >> symbol in module, or unknown parameter (see dmesg) >> >> >> Okay not sure what is up here, any suggestions? BTW, this is the correct >> module location and I manually ran depmod. >> >> thanks, >> randy >> >> _______________________________________________ >> Ocfs2-users mailing list >> Ocfs2-users@oss.oracle.com >> http://oss.oracle.com/mailman/listinfo/ocfs2-users >>
Appears ocfs2 fs module is not compatible with the other modules.... ocfs2_dlm.ko, ocfs2_nodemanager.ko, ocfs2_dlmfs.ko, configfs.ko. When you build the modules, ensure you copy all of them in /lib/modules/... before running depmod -a. Randy Ramsdell wrote:> Sunil Mushran wrote: > >> What does dmesg say? >> >> > I think it is suse thing, but not sure. > > FATAL: Error inserting ocfs2 > (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown > symbol in module, or unknown parameter (see dmesg) > dfb02010304:/usr/src # dmesg > ocfs2: disagrees about version of symbol dlm_print_one_lock > ocfs2: Unknown symbol dlm_print_one_lock > ocfs2: Unknown symbol o2hb_heartbeat_resource_get_by_name > ocfs2: disagrees about version of symbol dlmlock > ocfs2: Unknown symbol dlmlock > ocfs2: disagrees about version of symbol o2nm_get_node_by_num > ocfs2: Unknown symbol o2nm_get_node_by_num > ocfs2: disagrees about version of symbol o2hb_setup_callback > ocfs2: Unknown symbol o2hb_setup_callback > ocfs2: disagrees about version of symbol dlm_unregister_domain > ocfs2: Unknown symbol dlm_unregister_domain > ocfs2: disagrees about version of symbol dlm_register_domain > ocfs2: Unknown symbol dlm_register_domain > ocfs2: disagrees about version of symbol dlm_register_eviction_cb > ocfs2: Unknown symbol dlm_register_eviction_cb > ocfs2: disagrees about version of symbol config_item_put > ocfs2: Unknown symbol config_item_put > ocfs2: disagrees about version of symbol o2net_register_handler > ocfs2: Unknown symbol o2net_register_handler > ocfs2: disagrees about version of symbol o2hb_register_callback > ocfs2: Unknown symbol o2hb_register_callback > ocfs2: disagrees about version of symbol o2hb_unregister_callback > ocfs2: Unknown symbol o2hb_unregister_callback > ocfs2: disagrees about version of symbol dlmunlock > ocfs2: Unknown symbol dlmunlock > ocfs2: disagrees about version of symbol o2nm_node_put > ocfs2: Unknown symbol o2nm_node_put > > >> Randy Ramsdell wrote: >> >>> Hi, >>> >>> Everything compiled correctly for the ocfs2 package, but so far the >>> modules will not load with the "well known" module symbol error. >>> >>> FATAL: Error inserting ocfs2 >>> (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown >>> symbol in module, or unknown parameter (see dmesg) >>> >>> >>> Okay not sure what is up here, any suggestions? BTW, this is the correct >>> module location and I manually ran depmod. >>> >>> thanks, >>> randy >>> >>> _______________________________________________ >>> Ocfs2-users mailing list >>> Ocfs2-users@oss.oracle.com >>> http://oss.oracle.com/mailman/listinfo/ocfs2-users >>> >>> > > > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users@oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users >
Sunil Mushran wrote:> Appears ocfs2 fs module is not compatible with the other modules.... > ocfs2_dlm.ko, ocfs2_nodemanager.ko, ocfs2_dlmfs.ko, configfs.ko. > > When you build the modules, ensure you copy all of them in > /lib/modules/... > before running depmod -a. >topposting ouch. I found the issue. There are two locations that have the same named modules. /lib/modules/2.6.16.27-0.6-smp/extra/ocfs2/ <--- this is where the default "make install" puts them /lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ <--- these are the modules that are called with the init scripts etc ... So the choices are: 1. Compile kernel and remove ocfs2 <--- not really practical 2. Remove the offending ocfs2 modules. 3. Manually edit the modules.dep and remove the location of old modules. 4. Or have the "make install" portion store the modules in second location which overwrites the old. Where should this be addressed out of the four? Dealing with this as in number 4 seems the least like "cludge" unless the other distros standardize the location somewhere else. Or maybe do nothing and use packages only? example: vendor/ax2/ocfs2.spec-generic:EXTRA_MODLIB="${RPM_BUILD_ROOT}/lib/modules/%{kver}/extra" Thanks for your input Randy> Randy Ramsdell wrote: >> Sunil Mushran wrote: >> >>> What does dmesg say? >>> >>> >> I think it is suse thing, but not sure. >> >> FATAL: Error inserting ocfs2 >> (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown >> symbol in module, or unknown parameter (see dmesg) >> dfb02010304:/usr/src # dmesg >> ocfs2: disagrees about version of symbol dlm_print_one_lock >> ocfs2: Unknown symbol dlm_print_one_lock >> ocfs2: Unknown symbol o2hb_heartbeat_resource_get_by_name >> ocfs2: disagrees about version of symbol dlmlock >> ocfs2: Unknown symbol dlmlock >> ocfs2: disagrees about version of symbol o2nm_get_node_by_num >> ocfs2: Unknown symbol o2nm_get_node_by_num >> ocfs2: disagrees about version of symbol o2hb_setup_callback >> ocfs2: Unknown symbol o2hb_setup_callback >> ocfs2: disagrees about version of symbol dlm_unregister_domain >> ocfs2: Unknown symbol dlm_unregister_domain >> ocfs2: disagrees about version of symbol dlm_register_domain >> ocfs2: Unknown symbol dlm_register_domain >> ocfs2: disagrees about version of symbol dlm_register_eviction_cb >> ocfs2: Unknown symbol dlm_register_eviction_cb >> ocfs2: disagrees about version of symbol config_item_put >> ocfs2: Unknown symbol config_item_put >> ocfs2: disagrees about version of symbol o2net_register_handler >> ocfs2: Unknown symbol o2net_register_handler >> ocfs2: disagrees about version of symbol o2hb_register_callback >> ocfs2: Unknown symbol o2hb_register_callback >> ocfs2: disagrees about version of symbol o2hb_unregister_callback >> ocfs2: Unknown symbol o2hb_unregister_callback >> ocfs2: disagrees about version of symbol dlmunlock >> ocfs2: Unknown symbol dlmunlock >> ocfs2: disagrees about version of symbol o2nm_node_put >> ocfs2: Unknown symbol o2nm_node_put >> >> >>> Randy Ramsdell wrote: >>> >>>> Hi, >>>> >>>> Everything compiled correctly for the ocfs2 package, but so far the >>>> modules will not load with the "well known" module symbol error. >>>> >>>> FATAL: Error inserting ocfs2 >>>> (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown >>>> symbol in module, or unknown parameter (see dmesg) >>>> >>>> >>>> Okay not sure what is up here, any suggestions? BTW, this is the >>>> correct >>>> module location and I manually ran depmod. >>>> >>>> thanks, >>>> randy >>>> >>>> _______________________________________________ >>>> Ocfs2-users mailing list >>>> Ocfs2-users@oss.oracle.com >>>> http://oss.oracle.com/mailman/listinfo/ocfs2-users >>>> >> >> >> >> _______________________________________________ >> Ocfs2-users mailing list >> Ocfs2-users@oss.oracle.com >> http://oss.oracle.com/mailman/listinfo/ocfs2-users >>
I do 2. You could also look into adding the modules to /lib/modules/`uname -r`/update. I believe depmod searches that patch before the others. Randy Ramsdell wrote:> Sunil Mushran wrote: > >> Appears ocfs2 fs module is not compatible with the other modules.... >> ocfs2_dlm.ko, ocfs2_nodemanager.ko, ocfs2_dlmfs.ko, configfs.ko. >> >> When you build the modules, ensure you copy all of them in >> /lib/modules/... >> before running depmod -a. >> >> > > topposting ouch. > > I found the issue. There are two locations that have the same named > modules. > > /lib/modules/2.6.16.27-0.6-smp/extra/ocfs2/ <--- this is where the > default "make install" puts them > /lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ <--- these are the > modules that are called with the init scripts etc ... > > So the choices are: > > 1. Compile kernel and remove ocfs2 <--- not really practical > 2. Remove the offending ocfs2 modules. > 3. Manually edit the modules.dep and remove the location of old modules. > 4. Or have the "make install" portion store the modules in second > location which overwrites the old. > > Where should this be addressed out of the four? Dealing with this as in > number 4 seems the least like "cludge" unless the other distros > standardize the location somewhere else. Or maybe do nothing and use > packages only? > > example: > vendor/ax2/ocfs2.spec-generic:EXTRA_MODLIB="${RPM_BUILD_ROOT}/lib/modules/%{kver}/extra" > > > Thanks for your input > Randy > >> Randy Ramsdell wrote: >> >>> Sunil Mushran wrote: >>> >>> >>>> What does dmesg say? >>>> >>>> >>>> >>> I think it is suse thing, but not sure. >>> >>> FATAL: Error inserting ocfs2 >>> (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown >>> symbol in module, or unknown parameter (see dmesg) >>> dfb02010304:/usr/src # dmesg >>> ocfs2: disagrees about version of symbol dlm_print_one_lock >>> ocfs2: Unknown symbol dlm_print_one_lock >>> ocfs2: Unknown symbol o2hb_heartbeat_resource_get_by_name >>> ocfs2: disagrees about version of symbol dlmlock >>> ocfs2: Unknown symbol dlmlock >>> ocfs2: disagrees about version of symbol o2nm_get_node_by_num >>> ocfs2: Unknown symbol o2nm_get_node_by_num >>> ocfs2: disagrees about version of symbol o2hb_setup_callback >>> ocfs2: Unknown symbol o2hb_setup_callback >>> ocfs2: disagrees about version of symbol dlm_unregister_domain >>> ocfs2: Unknown symbol dlm_unregister_domain >>> ocfs2: disagrees about version of symbol dlm_register_domain >>> ocfs2: Unknown symbol dlm_register_domain >>> ocfs2: disagrees about version of symbol dlm_register_eviction_cb >>> ocfs2: Unknown symbol dlm_register_eviction_cb >>> ocfs2: disagrees about version of symbol config_item_put >>> ocfs2: Unknown symbol config_item_put >>> ocfs2: disagrees about version of symbol o2net_register_handler >>> ocfs2: Unknown symbol o2net_register_handler >>> ocfs2: disagrees about version of symbol o2hb_register_callback >>> ocfs2: Unknown symbol o2hb_register_callback >>> ocfs2: disagrees about version of symbol o2hb_unregister_callback >>> ocfs2: Unknown symbol o2hb_unregister_callback >>> ocfs2: disagrees about version of symbol dlmunlock >>> ocfs2: Unknown symbol dlmunlock >>> ocfs2: disagrees about version of symbol o2nm_node_put >>> ocfs2: Unknown symbol o2nm_node_put >>> >>> >>> >>>> Randy Ramsdell wrote: >>>> >>>> >>>>> Hi, >>>>> >>>>> Everything compiled correctly for the ocfs2 package, but so far the >>>>> modules will not load with the "well known" module symbol error. >>>>> >>>>> FATAL: Error inserting ocfs2 >>>>> (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown >>>>> symbol in module, or unknown parameter (see dmesg) >>>>> >>>>> >>>>> Okay not sure what is up here, any suggestions? BTW, this is the >>>>> correct >>>>> module location and I manually ran depmod. >>>>> >>>>> thanks, >>>>> randy >>>>> >>>>> _______________________________________________ >>>>> Ocfs2-users mailing list >>>>> Ocfs2-users@oss.oracle.com >>>>> http://oss.oracle.com/mailman/listinfo/ocfs2-users >>>>> >>>>> >>> >>> _______________________________________________ >>> Ocfs2-users mailing list >>> Ocfs2-users@oss.oracle.com >>> http://oss.oracle.com/mailman/listinfo/ocfs2-users >>> >>> > > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users@oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users >
Joel Becker wrote:> On Fri, Feb 09, 2007 at 04:55:21PM -0500, Randy Ramsdell wrote: > >> Ok. But do different vendors or at least the top three define different >> locations? >> >> Looking at the source from the ocfs2 package. >> >> I find: >> >> endor/rhel4/ocfs2.spec-generic:EXTRA_MODLIB="${RPM_BUILD_ROOT}/lib/modules/%{kver}/extra" >> vendor/rhel4/ocfs2.spec-generic:EXTRA_MODLIB="${RPM_BUILD_ROOT}/lib/modules/%{kver}smp/extra" >> vendor/rhel4/ocfs2.spec-generic:EXTRA_MODLIB="${RPM_BUILD_ROOT}/lib/modules/%{kver}hugemem/extra" >> vendor/rhel4/ocfs2.spec-generic:EXTRA_MODLIB="${RPM_BUILD_ROOT}/lib/modules/%{kver}largesmp/extra" >> >> So this looks like it is defined in the ocfs2 source although the vendor >> suppile modules are from a kernel compile as you say. >> > > Nononono. This is me *catching up* to make modules_install. > "make modules_install" doesn't use my EXTRA_MODLIB value. This is my > specfile storing off where we're going to copy modules from. Then they > copy them to the appropriate place in the vendor's tree. > That is (all paths are the installed paths, not the packaging > paths prefixed at RPM_BUILD_ROOT): > > 1) Actual module location is defined by vendor's kernel and is > rooted at /lib/modules/$(uname -r) > 2) Running "make modules_install" will put the modules at > /lib/modules/$(uname -r)/extra. > > 3) I define EXTRA_MODLIB to point to this, so I can then... > > 4) Copy from /lib/modules/$(uname -r)/extra to > /lib/modules/$(uname -r)/kernel/fs/ocfs2. > > It's a completely manual process that gets our modules to the > kernel/fs/ocfs2 location in our RPMs. > Why does SLES have them already in kernel/fs/ocfs2? Because > they are not building them externally. They patch the kernel sources > directly, and the kbuild infrastructure then treats them as "regular" > modules, not "external" modules. > > Joel > >Very nice explanation which explains everything, thanks. Since this be the case and assuming you want users to compile from scratch, would an install howto be in order? I would write a simple howto. Thanks, Randy Ramsdell