From owner-freebsd-qa Wed Mar 12 4:42:39 2003 Delivered-To: freebsd-qa@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7ED637B404; Wed, 12 Mar 2003 04:42:37 -0800 (PST) Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 363F143F3F; Wed, 12 Mar 2003 04:42:36 -0800 (PST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from goblet.cisco.com (IDENT:mirapoint@goblet.cisco.com [161.44.168.80]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h2CCgVSc000541; Wed, 12 Mar 2003 07:42:32 -0500 (EST) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [161.44.149.69]) by goblet.cisco.com (Mirapoint) with ESMTP id ACU10961; Wed, 12 Mar 2003 07:42:31 -0500 (EST) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.12.6/8.12.6) with ESMTP id h2CCgVFQ048951; Wed, 12 Mar 2003 07:42:31 -0500 (EST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <200303121242.h2CCgVFQ048951@bmcgover-pc.cisco.com> To: Hiroki Sato Cc: freebsd-sparc@FreeBSD.ORG, qa@FreeBSD.ORG Subject: Re: NFS problem? In-reply-to: Your message of "Wed, 12 Mar 2003 21:29:09 +0900." <20030312.212909.71544461.hrs@eos.ocn.ne.jp> Date: Wed, 12 Mar 2003 07:42:31 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have had one solid lockup in the i386<->i386 case during heavy NFS writes while moving large files (ISO images of CDs) back to the server after upgrading to 5.0 (client was also 5.0). I didn't have a debugger in the kernel at the time, and haven't reproduced it since I put it in to get a back trace/dump (~2 weeks now). I was waiting to post on the topic until I had some data to provide useful debugging, and to make sure it wasn't a fluke (new hardware, as well). I'll let the lists know if I see this again. > 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 fin e. > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message