Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co
!nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!news.k
rotte.org!fu-berlin.de!uni-berlin.de!not-for-mail
From: =?UTF-8?B?RGFuaWVsIFRyw7xtcGVy?=
Newsgroups: alt.os.linux.ubuntu
Subject: Re: NFS server broken by 6.10 upgrade
Date: Mon, 19 Feb 2007 17:31:49 +0100
Lines: 30
Message-ID: <45D9D0F5.3060904@gmx.de>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: news.uni-berlin.de qK1BDwa8SCIjSKx1XoBorAl/yrlTQvOtv/GEacRRXKDg0rd2s=
User-Agent: Thunderbird 1.5.0.9 (X11/20070103)
In-Reply-To:
X-Enigmail-Version: 0.94.1.1
Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:10674
-----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-----
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Omicron Theta BBS (1:261/20)
|
