From owner-freebsd-sparc Wed Mar 12 4:30:26 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 ABC3337B401 for ; Wed, 12 Mar 2003 04:30:25 -0800 (PST) Received: from smtp.eos.ocn.ne.jp (eos.ocn.ne.jp [211.6.83.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03A3E43F75 for ; Wed, 12 Mar 2003 04:30:25 -0800 (PST) (envelope-from hrs@eos.ocn.ne.jp) Received: from mail.allbsd.org (p54141-adsao12honb4-acca.tokyo.ocn.ne.jp [220.96.136.141]) by smtp.eos.ocn.ne.jp (Postfix) with ESMTP id 07A1E1900 for ; Wed, 12 Mar 2003 21:30:24 +0900 (JST) Received: from localhost (alph.allbsd.org [192.168.0.10]) by mail.allbsd.org (8.12.8/3.7W/DomainMaster) with ESMTP id h2CCTGqe092346 for ; Wed, 12 Mar 2003 21:29:18 +0900 (JST) (envelope-from hrs@eos.ocn.ne.jp) Date: Wed, 12 Mar 2003 21:29:09 +0900 (JST) Message-Id: <20030312.212909.71544461.hrs@eos.ocn.ne.jp> To: freebsd-sparc@FreeBSD.org Subject: NFS problem? From: Hiroki Sato X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 2.2 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 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? -- | Hiroki SATO / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message