After patching a vanilla 2.6.12.6 kernel with the Lustre patches for a vanilla 2.6.12 kernel, I get unknown symbols errors when loading the modules: llite: Unknown symbol ptlrpc_set_destroy llite: Unknown symbol lprocfs_read_frac_helper llite: Unknown symbol filp_open llite: Unknown symbol ldlm_lock_dump_handle llite: Unknown symbol lov_stripe_lock llite: Unknown symbol class_manual_cleanup llite: Unknown symbol mdc_set_open_replay_data llite: Unknown symbol ptlrpc_prep_set llite: Unknown symbol lustre_msg_string llite: Unknown symbol oig_init llite: Unknown symbol ldlm_cli_cancel_unused llite: Unknown symbol mdc_clear_open_replay_data llite: Unknown symbol l_lock llite: Unknown symbol mdc_setxattr llite: Unknown symbol mdc_getattr llite: Unknown symbol ptlrpc_queue_wait llite: Unknown symbol lbug_with_loc llite: Unknown symbol proc_lustre_root llite: Unknown symbol class_find_client_notype llite: Unknown symbol mdc_sync llite: Unknown symbol libcfs_assertion_failed llite: Unknown symbol libcfs_debug_msg llite: Unknown symbol ldlm_extent_shift_kms This goes on and on for lov, llite, mdc, ptlrpc, lnet, obdclass. The patches I applied were (with patch -Np1 < patch-name.patch, all hunks succeeded): lustre_version.patch vfs_intent-2.6.12.patch vfs_nointent-2.6.12.patch vfs_races-2.6.12.patch ext3-wantedi-misc-2.6-suse.patch jbd-2.6.10-jcberr.patch nfs-cifs-intent-2.6.12.patch iopen-misc-2.6.12.patch export-truncate-2.6-suse.patch export_symbols-2.6.12.patch dev_read_only-2.6-suse.patch export-2.6-suse.patch lookup_bdev_init_intent.patch 8kstack-2.6.12.patch remove-suid-2.6-suse.patch export-show_task-2.6-vanilla.patch sd_iostats-2.6-rhel4.patch fsprivate-2.6.patch export_symbol_numa.patch tcp-zero-copy-2.6.12.6.patch Is this a problem with my kernel? -- Jeremy Mann jeremy@biochem.uthscsa.edu University of Texas Health Science Center Bioinformatics Core Facility http://www.bioinformatics.uthscsa.edu Phone: (210) 567-2672
Hi Jeremy, These unknown symbols are fallout from dependent lustre modules failing to load. You need to find the first one (libcfs?) and see what it''s complaining about. Jim On Wed, 15 Nov 2006, Jeremy Mann wrote:> After patching a vanilla 2.6.12.6 kernel with the Lustre patches for a > vanilla 2.6.12 kernel, I get unknown symbols errors when loading the > modules: > > llite: Unknown symbol ptlrpc_set_destroy > llite: Unknown symbol lprocfs_read_frac_helper > llite: Unknown symbol filp_open > llite: Unknown symbol ldlm_lock_dump_handle > llite: Unknown symbol lov_stripe_lock > llite: Unknown symbol class_manual_cleanup > llite: Unknown symbol mdc_set_open_replay_data > llite: Unknown symbol ptlrpc_prep_set > llite: Unknown symbol lustre_msg_string > llite: Unknown symbol oig_init > llite: Unknown symbol ldlm_cli_cancel_unused > llite: Unknown symbol mdc_clear_open_replay_data > llite: Unknown symbol l_lock > llite: Unknown symbol mdc_setxattr > llite: Unknown symbol mdc_getattr > llite: Unknown symbol ptlrpc_queue_wait > llite: Unknown symbol lbug_with_loc > llite: Unknown symbol proc_lustre_root > llite: Unknown symbol class_find_client_notype > llite: Unknown symbol mdc_sync > llite: Unknown symbol libcfs_assertion_failed > llite: Unknown symbol libcfs_debug_msg > llite: Unknown symbol ldlm_extent_shift_kms > > This goes on and on for lov, llite, mdc, ptlrpc, lnet, obdclass. The > patches I applied were (with patch -Np1 < patch-name.patch, all hunks > succeeded): > > lustre_version.patch > vfs_intent-2.6.12.patch > vfs_nointent-2.6.12.patch > vfs_races-2.6.12.patch > ext3-wantedi-misc-2.6-suse.patch > jbd-2.6.10-jcberr.patch > nfs-cifs-intent-2.6.12.patch > iopen-misc-2.6.12.patch > export-truncate-2.6-suse.patch > export_symbols-2.6.12.patch > dev_read_only-2.6-suse.patch > export-2.6-suse.patch > lookup_bdev_init_intent.patch > 8kstack-2.6.12.patch > remove-suid-2.6-suse.patch > export-show_task-2.6-vanilla.patch > sd_iostats-2.6-rhel4.patch > fsprivate-2.6.patch > export_symbol_numa.patch > tcp-zero-copy-2.6.12.6.patch > > Is this a problem with my kernel? > > > -- > Jeremy Mann > jeremy@biochem.uthscsa.edu > > University of Texas Health Science Center > Bioinformatics Core Facility > http://www.bioinformatics.uthscsa.edu > Phone: (210) 567-2672 > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss@clusterfs.com > https://mail.clusterfs.com/mailman/listinfo/lustre-discuss >
Jim Garlick wrote:> Hi Jeremy, > > These unknown symbols are fallout from dependent lustre modules failing > to load. You need to find the first one (libcfs?) and see what it''s > complaining about.[root@alamo i386]# modprobe libcfs FATAL: Error inserting libcfs (/lib/modules/2.6.12.6-1smp/kernel/net/lustre/libcfs.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg: libcfs: Unknown symbol filp_open libcfs: Unknown symbol filp_open -- Jeremy Mann jeremy@biochem.uthscsa.edu University of Texas Health Science Center Bioinformatics Core Facility http://www.bioinformatics.uthscsa.edu Phone: (210) 567-2672
filp_open() should be exported in 2.6.12.6. Is it possible that your running kernel does not match the build environment you used for lustre (so symbol versions are not synced)? Jim On Wed, 15 Nov 2006, Jeremy Mann wrote:> > Jim Garlick wrote: >> Hi Jeremy, >> >> These unknown symbols are fallout from dependent lustre modules failing >> to load. You need to find the first one (libcfs?) and see what it''s >> complaining about. > > [root@alamo i386]# modprobe libcfs > FATAL: Error inserting libcfs > (/lib/modules/2.6.12.6-1smp/kernel/net/lustre/libcfs.ko): Unknown symbol > in module, or unknown parameter (see dmesg) > > dmesg: > > libcfs: Unknown symbol filp_open > libcfs: Unknown symbol filp_open > > > > -- > Jeremy Mann > jeremy@biochem.uthscsa.edu > > University of Texas Health Science Center > Bioinformatics Core Facility > http://www.bioinformatics.uthscsa.edu > Phone: (210) 567-2672 >
Jim Garlick wrote:> filp_open() should be exported in 2.6.12.6. > > Is it possible that your running kernel does not match the build > environment you used for lustre (so symbol versions are not synced)?[root@alamo ~]# uname -a Linux alamo.biochemistry.uthscsa.edu 2.6.12.6-1smp #1 SMP Tue Nov 14 16:16:49 CST 2006 i686 i686 i386 GNU/Linux [root@alamo lustre]# modinfo libcfs.ko filename: libcfs.ko author: Peter J. Braam <braam@clusterfs.com> description: Portals v3.1 license: GPL vermagic: 2.6.12.6-1smp SMP 686 REGPARM 4KSTACKS gcc-3.4 depends: lustre was compiled with --with-linux=/usr/src/linux-2.6 which is symlinked to 2.6.12.6-1smp. There''s one more thing I can try. The source tree is not where I compiled the kernel, rather I used the Rocks 4.2 way of building the kernel. I will recompile in /usr/src/linux-2.6 and recompile lustre. -- Jeremy Mann jeremy@biochem.uthscsa.edu University of Texas Health Science Center Bioinformatics Core Facility http://www.bioinformatics.uthscsa.edu Phone: (210) 567-2672
Jim, no luck with the recompiling, the same error happens. I wonder if it is a kernel config that I''m missing that is causing this. Do you (or anybody else) know how the kernel should be configured for the Lustre patch to work? Jim Garlick wrote:> filp_open() should be exported in 2.6.12.6. > > Is it possible that your running kernel does not match the build > environment you used for lustre (so symbol versions are not synced)? > > Jim > > On Wed, 15 Nov 2006, Jeremy Mann wrote: > >> >> Jim Garlick wrote: >>> Hi Jeremy, >>> >>> These unknown symbols are fallout from dependent lustre modules failing >>> to load. You need to find the first one (libcfs?) and see what it''s >>> complaining about. >> >> [root@alamo i386]# modprobe libcfs >> FATAL: Error inserting libcfs >> (/lib/modules/2.6.12.6-1smp/kernel/net/lustre/libcfs.ko): Unknown symbol >> in module, or unknown parameter (see dmesg) >> >> dmesg: >> >> libcfs: Unknown symbol filp_open >> libcfs: Unknown symbol filp_open >> >> >> >> -- >> Jeremy Mann >> jeremy@biochem.uthscsa.edu >> >> University of Texas Health Science Center >> Bioinformatics Core Facility >> http://www.bioinformatics.uthscsa.edu >> Phone: (210) 567-2672 >> >-- Jeremy Mann jeremy@biochem.uthscsa.edu University of Texas Health Science Center Bioinformatics Core Facility http://www.bioinformatics.uthscsa.edu Phone: (210) 567-2672
Try make rpms instead of make for lustre source. You will have to install the rpm after they are generated in /usr/src/redhat/RPMS. It should hopefully work if your kernel was patched and is working fine. If not, you will have to do the same for your kernel source too. On Wed, 2006-11-15 at 14:50 -0600, Jeremy Mann wrote:> Jim, no luck with the recompiling, the same error happens. I wonder if it > is a kernel config that I''m missing that is causing this. Do you (or > anybody else) know how the kernel should be configured for the Lustre > patch to work? > > > Jim Garlick wrote: > > filp_open() should be exported in 2.6.12.6. > > > > Is it possible that your running kernel does not match the build > > environment you used for lustre (so symbol versions are not synced)? > > > > Jim > > > > On Wed, 15 Nov 2006, Jeremy Mann wrote: > > > >> > >> Jim Garlick wrote: > >>> Hi Jeremy, > >>> > >>> These unknown symbols are fallout from dependent lustre modules failing > >>> to load. You need to find the first one (libcfs?) and see what it''s > >>> complaining about. > >> > >> [root@alamo i386]# modprobe libcfs > >> FATAL: Error inserting libcfs > >> (/lib/modules/2.6.12.6-1smp/kernel/net/lustre/libcfs.ko): Unknown symbol > >> in module, or unknown parameter (see dmesg) > >> > >> dmesg: > >> > >> libcfs: Unknown symbol filp_open > >> libcfs: Unknown symbol filp_open > >> > >> > >> > >> -- > >> Jeremy Mann > >> jeremy@biochem.uthscsa.edu > >> > >> University of Texas Health Science Center > >> Bioinformatics Core Facility > >> http://www.bioinformatics.uthscsa.edu > >> Phone: (210) 567-2672 > >> > > > >
verify kernel patches was applied without errors and filp_open is exported by kernel. ==# grep filp_open open.c struct file *filp_open(const char * filename, int flags, int mode) EXPORT_SYMBOL(filp_open); struct file *f = filp_open(tmp, flags, mode); ==if you kernel source don`t have "EXPORT_SYMBOL(filp_open)" please add it by hand. ? ???, 15.11.2006, ? 22:50, Jeremy Mann ?????:> Jim, no luck with the recompiling, the same error happens. I wonder if it > is a kernel config that I''m missing that is causing this. Do you (or > anybody else) know how the kernel should be configured for the Lustre > patch to work? > > > Jim Garlick wrote: > > filp_open() should be exported in 2.6.12.6. > > > > Is it possible that your running kernel does not match the build > > environment you used for lustre (so symbol versions are not synced)? > > > > Jim > > > > On Wed, 15 Nov 2006, Jeremy Mann wrote: > > > >> > >> Jim Garlick wrote: > >>> Hi Jeremy, > >>> > >>> These unknown symbols are fallout from dependent lustre modules failing > >>> to load. You need to find the first one (libcfs?) and see what it''s > >>> complaining about. > >> > >> [root@alamo i386]# modprobe libcfs > >> FATAL: Error inserting libcfs > >> (/lib/modules/2.6.12.6-1smp/kernel/net/lustre/libcfs.ko): Unknown symbol > >> in module, or unknown parameter (see dmesg) > >> > >> dmesg: > >> > >> libcfs: Unknown symbol filp_open > >> libcfs: Unknown symbol filp_open > >> > >> > >> > >> -- > >> Jeremy Mann > >> jeremy@biochem.uthscsa.edu > >> > >> University of Texas Health Science Center > >> Bioinformatics Core Facility > >> http://www.bioinformatics.uthscsa.edu > >> Phone: (210) 567-2672 > >> > >-- Alexey Lyashkov <shadow@clusterfs.com> Beaver team