[Linux-cluster] no version for "gfs2_unmount_lockproto"

Bob Peterson rpeterso at redhat.com
Tue Feb 12 18:34:34 UTC 2008


On Tue, 2008-02-12 at 19:13 +0100, Wagner Ferenc wrote:
> Hi,
> 
> I've compiled cluster-2.01.00 against Linux 2.6.23.16.  On modprobe
> gfs I got the following two kernel messages:
> 
> gfs: no version for "gfs2_unmount_lockproto" found: kernel tainted.
> GFS 2.01.00 (built Feb 12 2008 14:42:50) installed

Hi Wagner,

The HEAD / RHEL5 / (similar) versions of GFS use part of gfs2's
locking infrastructure.  For RHEL5, we did a patch to export
those symbols from GFS2.  The patch looks like the one I have
below.  So the GFS2 module has to be loaded for GFS to work
and that's just so GFS and GFS2 share the same locking protocol.
(i.e. people can mount both gfs and gfs2 at the same time and
go through the same dlm).  The exporting of those symbols did
not get pushed into upstream GFS2 because it's only needed for
GFS(1), which itself isn't part of the upstream kernel.

If you add these symbol exports to GFS2 it should allow GFS
to mount properly.

Regards,

Bob Peterson
Red Hat GFS
--
--- a/fs/gfs2/locking.c	2008-02-11 11:10:57.000000000 -0600
+++ b/fs/gfs2/locking.c	2008-02-08 14:10:36.000000000 -0600
@@ -181,4 +181,6 @@ void gfs2_withdraw_lockproto(struct lm_l
 
 EXPORT_SYMBOL_GPL(gfs2_register_lockproto);
 EXPORT_SYMBOL_GPL(gfs2_unregister_lockproto);
-
+EXPORT_SYMBOL_GPL(gfs2_withdraw_lockproto);
+EXPORT_SYMBOL_GPL(gfs2_mount_lockproto);
+EXPORT_SYMBOL_GPL(gfs2_unmount_lockproto);





More information about the Linux-cluster mailing list