On Mon, Nov 15, 2004 at 05:30:05PM -0500, Shih-Che Huang wrote: > Hi Adam, > Where can I find the moudles which match my kernel? > I am using CentOS3.3 2.4.21-20.EL.c0 . Good question. The GFS-6.0 rpms from Red Hat's site are for Red Hat kernels. If you are unable to use a Red Hat kernel that matches the GFS rpms, then you will either need to compile GFS from source, or bug your distribution's package maintainers. > On Mon, 15 Nov 2004 14:44:30 -0600, Adam Manthei <amanthei@xxxxxxxxxx> wrote: > > On Mon, Nov 15, 2004 at 03:33:03PM -0500, Shih-Che Huang wrote: > > > > > > > Hi, > > > I am running CentOS 3.3 2.4.21-20.EL.c0 and want to load the modules > > > for GFS 6.0. > > > It came back followin message when I type "modprobe lock_guld" > > > and "modprobe gfs". > > > > > > # modprobe lock_gulm > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs_locking/lock_gulm/lock_gulm.o: > > > unresolved symbol sock_recvmsg_Racb84c2d > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs_locking/lock_gulm/lock_gulm.o: > > > unresolved symbol sock_sendmsg_R808aeb7d > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs_locking/lock_gulm/lock_gulm.o: > > > unresolved symbol sock_release_R95b5793b > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs_locking/lock_gulm/lock_gulm.o: > > > unresolved symbol sock_create_Raed60fac > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs_locking/lock_gulm/lock_gulm.o: > > > insmod /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs_locking/lock_gulm/lock_gulm.o > > > failed > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs_locking/lock_gulm/lock_gulm.o: > > > insmod lock_gulm failed > > > > > > # modprobe gfs > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs/gfs.o: unresolved symbol > > > irq_stat_R94d0d943 > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs/gfs.o: insmod > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs/gfs.o failed > > > /lib/modules/2.4.21-20.EL.c0/kernel/fs/gfs/gfs.o: insmod gfs failed > > > > > > Any idea? > > > > > > Thanks for your help! > > > > The modules you are loading were not built against the same source and/or > > .config as your kernel as evident by the symbol names are unresolved: > > > > unresolved symbol irq_stat_R94d0d943 > > unresolved symbol sock_recvmsg_Racb84c2d > > unresolved symbol sock_sendmsg_R808aeb7d > > unresolved symbol sock_release_R95b5793b > > unresolved symbol sock_create_Raed60fac > > > > -- > > Adam Manthei <amanthei@xxxxxxxxxx> > > > > > -- > Shih-Che Huang -- Adam Manthei <amanthei@xxxxxxxxxx>
