From owner-freebsd-stable  Wed May 20 10:32:01 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA07974
          for freebsd-stable-outgoing; Wed, 20 May 1998 10:32:01 -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 KAA07936
          for <freebsd-stable@freebsd.org>; Wed, 20 May 1998 10:31:51 -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 0ycCfo-0001Ar-00; Wed, 20 May 1998 18:29:04 +0100
Message-ID: <356312DF.560EE29F@doc.ic.ac.uk>
Date: Wed, 20 May 1998 18:29:03 +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: dg@root.com
CC: freebsd-stable@FreeBSD.ORG
Subject: Re: post-crash fsck failing with DUP inodes
References: <199805200112.SAA29357@implode.root.com>
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.
...
>    A bug that caused a problem like the above was just recently fixed in
> both -current and -stable.

You're right.  The description of the problem at

	http://www.freebsd.org/cgi/query-pr.cgi?pr=6611

fits the symptoms I've seen here.  The Problem Report is also a good
read - congratulations to Stephen Clawson for solving what looks like a
subtle and nasty bug!

Many thanks,
Mark

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