From owner-freebsd-alpha Thu Nov 29 7:38:13 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E593B37B421 for ; Thu, 29 Nov 2001 07:38:06 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA12245; Thu, 29 Nov 2001 10:38:02 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id fATFbap85409; Thu, 29 Nov 2001 10:37:36 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15366.22080.471677.562171@grasshopper.cs.duke.edu> Date: Thu, 29 Nov 2001 10:37:36 -0500 (EST) To: Paul Herman Cc: freebsd-alpha@freebsd.org Subject: Re: NFS Kernel Panic. Unaligned Access? In-Reply-To: <200111290217.fAT2HZQ01665@tick.sc.omation.com> References: <15365.32857.392495.737510@grasshopper.cs.duke.edu> <200111290217.fAT2HZQ01665@tick.sc.omation.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Paul Herman writes: > On Wed, 28 Nov 2001, Andrew Gallatin wrote: > > > Can you characterize your environment a little more? > > Hi Drew, > > Thanks for the in-depth explanation. > > A little about the environment: the client is 4.4-RELEASE alpha and > the server is 4.3-RELEASE i386 both with NFS compiled in kernel. > The mount point using NFSv3 over TCP: > > tick$ df /usr/home > Filesystem 1K-blocks Used Avail Capacity Mounted on > fs2:/u01/home 551540862 467896476 39521118 92% /usr/home > > At the time it was crashing, it was a particular file. Every time > after reboot I tried to access it, it panic'ed. I went to lunch > this afternoot, came back, and since then I couldn't reproduce it. > I will try again tomorrow, and if I do I'll post a tcpdump. The more that I think about it, the less I think that a TCP dump would help -- the client is forming a read rpc, so it hasn't talked to the server yet for this particular transaction. If it keeps happening, can you switch to UDP & see if it goes away? Its a lot faster in most cases, and since I've never seen this with 10+ alphas over 2 years running NFS over UDP, I'm figuring it might be safer.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message