From owner-freebsd-hackers Sat Jun 10 03:29:58 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA05070 for hackers-outgoing; Sat, 10 Jun 1995 03:29:58 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA05063 for ; Sat, 10 Jun 1995 03:29:55 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id DAA10075; Sat, 10 Jun 1995 03:33:14 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id DAA10595; Sat, 10 Jun 1995 03:30:08 -0700 Message-Id: <199506101030.DAA10595@corbin.Root.COM> To: "Clay D. Hopperdietzel" cc: hackers@freebsd.org Subject: Re: NFS bug in -current ? In-reply-to: Your message of "Fri, 09 Jun 95 14:56:57 CDT." <199506091956.OAA01019@anvil.appsmiths.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 10 Jun 1995 03:30:06 -0700 Sender: hackers-owner@freebsd.org Precedence: bulk >I've been just hammering away at NFS (like applying all the CTM updates >since 2.0R) and haven't had a single problem. > >I also was trying to install some stuff onto a NFS served /usr/local/bin >directory. When I get to the same point (looks like an install to the NFS >mounted directory from the client), the box who is serving panics with >something to the effect of 'bf_deallocate: object deleted too many times'. It's a known problem that I recently fixed. It happens whenever you create a hard link on NFS. There is another, much more rare and difficult to manifest bug (takes 3-8 hours of continuous NFS file I/O) that causes the client to fail with the same panic. It seems to only occur when multiple processes are accessing the same file concurrently. I've been able to reproduce this one twice in the past 24 hours - collecting more information each time - and should hopefully have a fix in a few days. -DG