Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!newsfe   
   d.freenet.de!feeder.news-service.com!newsgate.cistron.nl!xs4all!   
   ews.tele.dk!news.tele.dk!small.news.tele.dk!sn-xt-sjc-02!sn-xt-s   
   c-09!sn-post-sjc-01!supernews.com!corp.supernews.com!not-for-mail   
   From: Michael Hopkins    
   Newsgroups: alt.os.linux.ubuntu   
   Subject: Re: NFS server broken by 6.10 upgrade   
   Date: Tue, 20 Feb 2007 00:18:23 +0000   
   Organization: Posted via Supernews, http://www.supernews.com   
   Message-ID:    
   User-Agent: Microsoft-Entourage/11.3.3.061214   
   Thread-Topic: NFS server broken by 6.10 upgrade   
   Thread-Index: AcdUhKHH4FAq+MB3EduEwgAX8gBuJA==   
   References:    
   <45D9D110.7040001@gmx.de>   
   Mime-version: 1.0   
   Content-Type: text/plain; charset="ISO-8859-1"   
   Content-transfer-encoding: 8bit   
   X-Complaints-To: abuse@supernews.com   
   Lines: 66   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:10708   
      
   On 19/2/07 16:32, in article 45D9D110.7040001@gmx.de, "Daniel Trümper"   
    wrote:   
      
   > -----BEGIN PGP SIGNED MESSAGE-----   
   > Hash: SHA1   
   >    
   > Dear Michael,   
   >    
   >> Just upgraded server from 6.06 to 6.10 and, along with all the usual   
   >> problems others have mentioned (xorg, perl/en etc.) the NFS server which has   
   >> been rock-solid on the Mac network for a long time has stopped working.   
   >>    
   >> Sometimes it's there but flaky, other times nothing.  Have tried a lot with   
   >> firewalls, different versions (2-4), different client mount options etc but   
   >> nothing seems to be doing the trick.   
   >>    
   >> Any advice on diagnosis or solution greatly appreciated.  Is it possible to   
   >> downgrade some components to give me NFS again without going back completely   
   >> to 6.06?  Don't mind compiling from source etc if necessary.   
   > To me this somehow sounds like firewall and the port thing. Did you set   
   > the ports for the lockd as kernel parameters? It might be that during   
   > the upgrade your kernel got replaced and if you set the kernel options   
   > directly inside the "kernel" line of your /boot/grub/menu.lst this line   
   > is lost and you cannot fix the port anymore.   
   >    
   > Daniel   
   > -----BEGIN PGP SIGNATURE-----   
   > Version: GnuPG v1.4.3 (GNU/Linux)   
   >    
   > iD8DBQFF2dD1taNKlGovncgRAoLIAKCUX3x3VDUwOzxMgn6/PvZ1199NewCgoLiG   
   > v53/gBKHXLXd3vAeEPz0TWY=   
   > =lhmM   
   > -----END PGP SIGNATURE-----   
      
      
   Hi Daniel   
      
   Thanks for replying.   
      
   How do I diagnose and/or change this?   
      
   I have set static ports for the various NFS daemons and matched those to the   
   firewall on both client and server.  The ports I set them to were confirmed   
   in Œrpcinfo ­p¹. Also, turning both firewalls off completely makes no   
   difference.   
      
   Searching on Ubuntu forums with ŒNFS 6.10¹ it appears that I am not alone.   
   :o\   
      
   I have now tried a few alternative kernels but still no solution.   
      
   M   
      
      
      
   _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/   
      
           _/    _/   _/_/_/             Hopkins Research Ltd   
          _/    _/   _/    _/   
         _/_/_/_/   _/_/_/          http://www.hopkins-research.com/   
        _/    _/   _/   _/   
       _/    _/   _/     _/               'touch the future'   
                         
   _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/   
      
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)