Re: [gentoo-user] HP Cluster on Gentoo

["Boyd Stephen Smith Jr." <bss03@volumehost.net>]

[-- Attachment #1: Type: text/plain, Size: 3339 bytes --]

On Tuesday 20 February 2007, Hans-Stefan Bauer <hsbauer@uni-hohenheim.de> 
wrote about 'Re: [gentoo-user] HP Cluster on Gentoo':
> Hallo,
>
> Boyd Stephen Smith Jr. schrieb:
> > On Monday 19 February 2007 02:47, Hans-Stefan Bauer wrote:
> >> storm1 hsbauer # /etc/init.d/gfs start
> >>  * Starting gfs cluster:
> >>  * Loading lock_dlm kernel module ...
> >> FATAL: Error inserting lock_dlm
> >> (/fs/gfs_locking/lock_dlm/lock_dlm.ko): Unknown symbol in module, or
> >> unknown parameter (see dmesg)
> >>  * Failed to load lock_dlm kernel
> >> module                                   [ !! ]
> >
> > Check your kernel configuration, particularly the "Distributed Lock
> > Manager"
> > option, CONFIG_DLM.  You may need that part of mainline so that your
> > out-of-tree module works.
>
> Thank you for the fast answer. I looked into the file
> "/usr/src/linux/.config". There is no variable CONFIG_DLM in it. Also
> with a "make menuconfig" I did not find a possibility to select it.

Here's the search results against my running kernel (2.6.19-gentoo-r2).

Symbol: DLM [=n]
Prompt: Distributed Lock Manager (DLM)
  Defined at fs/dlm/Kconfig:4
  Depends on: INET && IP_SCTP && EXPERIMENTAL && (IPV6 || IPV6=n)
  Location:
    -> File systems
      -> Distributed Lock Manager
  Selects: CONFIGFS_FS
  Selected by: GFS2_FS_LOCKING_DLM && BLOCK && GFS2_FS

I was unable to find it in my older kernel (2.6.18-gentoo), so perhaps a 
kernel upgrade could solve (part of) your issue.  Of course, any 
out-of-tree modules will have to be compiled after you fix up 
your /usr/src/linux symlink.  'module-rebuild' can help with that.

2.6.19-gentoo-r2 also provides:

Symbol: GFS2_FS_LOCKING_DLM [=n]
Prompt: GFS2 DLM locking module
  Defined at fs/gfs2/Kconfig:34
  Depends on: BLOCK && GFS2_FS
    Location:
     -> File systems
       -> GFS2 file system support (GFS2_FS [=n])
   Selects: DLM

Which probably makes sys-cluster/gfs-kernel unecessary, too.

> >> Apart from the occurring problem it is strange for me that emerge
> >> installs the kernel module into the root directory of the system (see
> >> error message above) and not into "/lib/modules/..." as I would
> >> expect.
> >
> > Hrm, double-check (by looking at your filesystem) to make sure it's in
> > the wrong place.  If so, please file a bug, that behavior is broken.
>
> I redirected the output of an emerge into a file with the following
> command:

I might look at this, but the easiest way to see if it's in the wrong 
location is just find it on the filesystem.  (I don't trust the output of 
emerge all the time anyway -- some packages do stupid things like ignoring 
$ROOT and whotnot.)

>  >>> /cluster/dlm.ko

Hrm, make sure this is modprobed before gfs tries to load lock_dlm.  That 
might solve your issue without a kernel upgrade.  In my first post, I 
didn't consider the fact that you have sys-cluster/dlm-kernel (which 
provides the out-of-tree dlm.ko) despite the fact that you mentioned it.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     
New GPG Key!  Old key expires 2007-03-25.  Upgrade NOW!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]