From owner-freebsd-sparc Wed Mar 12 8:32:10 2003 Delivered-To: freebsd-sparc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57FE737B404 for ; Wed, 12 Mar 2003 08:32:09 -0800 (PST) Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFF4643F85 for ; Wed, 12 Mar 2003 08:32:07 -0800 (PST) (envelope-from jake@k6.locore.ca) Received: from k6.locore.ca (localhost.locore.ca [127.0.0.1]) by k6.locore.ca (8.12.8/8.12.8) with ESMTP id h2CGZkxS053669; Wed, 12 Mar 2003 11:35:46 -0500 (EST) (envelope-from jake@k6.locore.ca) Received: (from jake@localhost) by k6.locore.ca (8.12.8/8.12.8/Submit) id h2CGZjXX053668; Wed, 12 Mar 2003 11:35:45 -0500 (EST) Date: Wed, 12 Mar 2003 11:35:45 -0500 From: Jake Burkholder To: Hiroki Sato Cc: freebsd-sparc@FreeBSD.ORG Subject: Re: NFS problem? Message-ID: <20030312113545.A50948@locore.ca> References: <20030312.212909.71544461.hrs@eos.ocn.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 +0900 Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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