From owner-freebsd-stable  Tue May 19 18:13:23 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA04269
          for freebsd-stable-outgoing; Tue, 19 May 1998 18:13:23 -0700 (PDT)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04208
          for <freebsd-stable@FreeBSD.ORG>; Tue, 19 May 1998 18:13:02 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA29357;
	Tue, 19 May 1998 18:12:54 -0700 (PDT)
Message-Id: <199805200112.SAA29357@implode.root.com>
To: Mark Dawson <md@doc.ic.ac.uk>
cc: freebsd-stable@FreeBSD.ORG
Subject: Re: post-crash fsck failing with DUP inodes 
In-reply-to: Your message of "Tue, 19 May 1998 22:44:31 BST."
             <3561FD3F.D1B21BF6@doc.ic.ac.uk> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 19 May 1998 18:12:54 -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk

>The fileserver I run using 2.2.6-stable is crashing after 3-4 weeks.  On
>rebooting there is typically a DUP inode problem with filesystems that
>have heavy NFS use.  The filesystem inconsistency appears to be caused
>some time prior to the crash and is only shown up by a post-crash fsck. 
>Has anyone else seen this problem or have ideas on where I should
>concentrate my efforts towards a solution?  [I can provide more system
>configuration details on request.]

   A bug that caused a problem like the above was just recently fixed in
both -current and -stable.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message