OpenVZ Forum


Home » General » Support » gfs does not compile with openvz kernel
gfs does not compile with openvz kernel [message #4931] Thu, 03 August 2006 10:10 Go to next message
da_matthew
Messages: 2
Registered: August 2006
Junior Member
Hello everyone.

I am currently trying to set up a new small server cluster with two servers running OpenVZ (and several VEs each) and a drbd 8.0pre4/gfs 1.02.00 combination to get the data redundant and available on every machine. (coda/nfs/openafs aren't really an option, iSCSI/gfs does not provide the required redundancy as far as I can tell)

The problem so far is, gfs does compile fine with a vanilla kernel but fails with a OpenVZ kernel (2.6.16-026test015) on a fresh and up-2-date Gentoo x86_64 system with gcc 4.1.1:

/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/eaops.c: In function 'user_eo_get':
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/eaops.c:72: error: too few arguments to function 'permission'
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/eaops.c: In function 'user_eo_set':
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/eaops.c:95: error: too few arguments to function 'permission'
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/eaops.c: In function 'user_eo_remove':
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/eaops.c:120: error: too few arguments to function 'permission'
make[4]: *** [/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/eaops.o] Error 1
make[4]: *** Waiting for unfinished jobs....
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/dio.c: In function 'stuck_releasepage':
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/dio.c:85: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'sector_t'
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/dio.c:96: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t'
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/dio.c:122: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'uint64_t'
/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs/dio.c:122: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t'
make[3]: *** [_module_/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs] Error 2
make[3]: Leaving directory `/usr/src/linux-2.6.16-openvz-026.015-r2'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src/gfs'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/gfs-kernel-1.02.00-r1/work/cluster-1.02.00/gfs-kernel/src'
make: *** [all] Error 2


Has anyone successfully got gfs (1.02.00) working on a system based on a OpenVZ kernel?

Thanks for any help in advance...
Re: gfs does not compile with openvz kernel [message #4932 is a reply to message #4931] Thu, 03 August 2006 10:39 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
The problem is that in OpenVZ kernel one more argument is added to the function permission(). While gfs sources uses the original linux kernel definition of this function.

You can manually try to add last argument "NULL" to all calls of permission() function in gfs sources...
However the consequences of such modiffication is unexpected without deeper analysis: gfs developers write this kernel module for vanilla, not OpenVZ kernel.
Re: gfs does not compile with openvz kernel [message #4933 is a reply to message #4932] Thu, 03 August 2006 10:53 Go to previous message
da_matthew
Messages: 2
Registered: August 2006
Junior Member
I see. That's not quite the solution for a production system. I guess that makes gfs unavailable for us. Unfortunately I am running out of options how to realize what we had planed to do with our servers. Sad

Well that means back to the sketch board for me- again. Thanks for the information btw!
Previous Topic: VE "route" command shows 191.255.255.1
Next Topic: *SOLVED* FC3 p2v migration
Goto Forum:
  


Current Time: Wed Nov 06 09:05:08 GMT 2024

Total time taken to generate the page: 0.04544 seconds