From owner-freebsd-stable  Tue May 19 14:44:57 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA22709
          for freebsd-stable-outgoing; Tue, 19 May 1998 14:44:57 -0700 (PDT)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from fox.doc.ic.ac.uk (fox.doc.ic.ac.uk [146.169.1.1])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA22669
          for <freebsd-stable@freebsd.org>; Tue, 19 May 1998 14:44:38 -0700 (PDT)
          (envelope-from md@doc.ic.ac.uk)
Received: from doc.ic.ac.uk [146.169.1.33] 
	by fox.doc.ic.ac.uk with esmtp (Exim 1.73 #1)
	id 0ybuBU-0002qa-00; Tue, 19 May 1998 22:44:32 +0100
Message-ID: <3561FD3F.D1B21BF6@doc.ic.ac.uk>
Date: Tue, 19 May 1998 22:44:31 +0100
From: Mark Dawson <md@doc.ic.ac.uk>
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.32 i586)
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
Subject: post-crash fsck failing with DUP inodes
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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.]

Many thanks,
Mark

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