Date: Wed, 12 Mar 2003 11:35:45 -0500 From: Jake Burkholder <jake@locore.ca> To: Hiroki Sato <hrs@eos.ocn.ne.jp> Cc: freebsd-sparc@FreeBSD.ORG Subject: Re: NFS problem? Message-ID: <20030312113545.A50948@locore.ca> In-Reply-To: <20030312.212909.71544461.hrs@eos.ocn.ne.jp>; from hrs@eos.ocn.ne.jp on Wed, Mar 12, 2003 at 09:29:09PM %2B0900 References: <20030312.212909.71544461.hrs@eos.ocn.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Apparently, On Wed, Mar 12, 2003 at 09:29:09PM +0900, Hiroki Sato said words to the effect of; > Hi, > > I experienced an NFS problem between an i386 box and a sparc64 box. > The i386 box that is running 5-CURRENT as of Mar 7 acts as an NFS server, > and the sparc64 box that is running 5-CURRENT as of Mar 5 acts > as an NFS client. The problem is that the server is locked up > under heavy loads such as doing make release. Once locked, > it is not responsive to outcoming ssh connection request and so on, > and I had to reboot the box... > > A friend of mine told me in an i386(server)<->i386(client) case > it was OK under heavy loads, and I confirmed that in an > i386(server, 4-STABLE)<->sparc64(client, 5-CURRENT) case it also worked fine. > As far as I can check, the problem seems to happen in an > i386(server, 5-CURRENT)<->sparc64(client, 5-CURRENT) case only. > > I don't know what is the trigger, but did anyone experience > the same problem? Kris Kennaway has reported a similar problem, but iirc it was the opposite; with 4.x the server would crash and upgrading it to 5.0 fixed it. I have no idea what could cause it though. I use nfs pretty heavily between my sparc64 development machines and a 4.x x86 server and have never seen this. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030312113545.A50948>