[UCLA-LUG] NFS

Frederick Lee phaethon@fire.csua.ucla.edu
Thu, 6 Apr 2000 20:54:45 -0700


On Thu, 6 Apr 2000 19:43:30 -0700 (PDT), said "LEE,JAMES WOON" <jwlee@ucla.edu>
>That didn't help... cat /proc/filesystems shows the following:
>
>	ext2
>nodev	proc
>	iso9660
>nodev	devpts
>
>No nfs...?  Recompile?

Funny.  I thought kerneld would have automagically loaded nfs.o...

Try
bash# modprobe nfs

If that doesn't work... you mentioned recompiling; I presume that you've
already custom-compiled a kernel.  If so, you may not have to recompile the
entire kernel, but just the NFS modules.

Go over to kernel source, run "make menuconfig" (or xconfig if preferred).
Select NFS (under Filesystems, Network Filesystems) as module.
Save the configuration, then run:
  make dep   (dunno if this is needed)
  make modules
  make modules_install
  depmod -a

(Note that [b]zImage is skipped!)

You don't need to recompile the kernel, just the module(s).  Once having done
so, you should be able to insert the nfs module (without rebooting), with
the above modprobe command.

If you get masses of "unresolved symbols ..." messages, you can either try
forcing it with "modprobe -f nfs", or recompiling the entire kernel, kit and
kaboodle, which should resync all the symbol names, then booting into the
new(er) kernel.



On Thu, 06 Apr 2000 20:10:53 -0700, said James Lee <jwlee@ucla.edu>:
>[root@cypress mydoc]# /etc/rc.d/init.d/nfs start
>Starting NFS services:                                     [  OK  ]
>Starting NFS statd:
>Starting NFS quotas:
>Starting NFS mountd:
>mountd: couldn't stat /var/lib/nfs/xtab
>                                                           [FAILED]
>Starting NFS daemon:
>nfssvc: Address already in use
^^^^ Hrmm... nfsd already running before... perhaps that wasn't part of
the problem.

>                                                           [FAILED]
>[root@cypress mydoc]#
>
>That /proc/filesystems I just sent was for both machines.  Thanks!
[snip]



-Fred