David Siroky wrote:
Hi! I tried to compile the cluster 1.02 against debian kernel 2.6.15 ./configure --kernel_src=/usr/src/linux-source-2.6.15 make install but the compilation fails: .... /usr/src/cluster-1.02.00/gfs-kernel/src/gfs/ops_file.c: In function 'gfs_write': /usr/src/cluster-1.02.00/gfs-kernel/src/gfs/ops_file.c:955: warning: implicit declaration of function 'mutex_lock' /usr/src/cluster-1.02.00/gfs-kernel/src/gfs/ops_file.c:955: error: 'struct inode' has no member named 'i_mutex' /usr/src/cluster-1.02.00/gfs-kernel/src/gfs/ops_file.c:960: warning: implicit declaration of function 'mutex_unlock' /usr/src/cluster-1.02.00/gfs-kernel/src/gfs/ops_file.c:960: error: 'struct inode' has no member named 'i_mutex' make[5]: *** [/usr/src/cluster-1.02.00/gfs-kernel/src/gfs/ops_file.o] Error 1 make[4]: *** [_module_/usr/src/cluster-1.02.00/gfs-kernel/src/gfs] Error 2 make[4]: Leaving directory `/usr/src/linux-source-2.6.15' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/cluster-1.02.00/gfs-kernel/src/gfs' ... What em I doing wrong?
This is why we've been very careful about RHEL updates (in order to provide stable external interfaces and environment for users and customers).
Sometime after 2.6.15 kernel, the i_sem semaphore within VFS layer's struct inode was changed to i_mutext in community versions of kernels. GFS had to comply to this change for non-RHEL based CVS branches. In short, you have to pick up newer versions of kernel from your distributor that contains this VFS layer changes.
-- Wendy -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
