From nemesis!uhclem@fw.ast.com  Sun Apr  9 13:13:48 1995
Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01109
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 9 Apr 1995 13:13:46 -0700
Received: from ast.com by relay1.UU.NET with SMTP 
	id QQyktk25391; Sun, 9 Apr 1995 16:13:41 -0400
Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA08900
  (5.67b/IDA-1.5 for uunet!freebsd.org!FreeBSD-gnats-submit); Sun, 9 Apr 1995 13:17:48 -0700
Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1)
	id <m0ry3FH-0000HMC@trsvax.fw.ast.com>; Sun, 9 Apr 95 15:06 CDT
Received: by nemesis.lonestar.org (Smail3.1.27.1 #18)
	id m0ry1yH-0004vsC; Sun, 9 Apr 95 13:44 CDT
Message-Id: <m0ry1yH-0004vsC@nemesis.lonestar.org>
Date: Sun, 9 Apr 95 13:44 CDT
From: uhclem%nemesis@fw.ast.com
Reply-To: uhclem%nemesis@fw.ast.com
To: FreeBSD-gnats-submit@freebsd.org
Cc: uhclem@nemesis.lonestar.org
Subject: Creating lost+found causes fsck to stop fsck -y	FDIV017
X-Send-Pr-Version: 3.2

>Number:         323
>Category:       bin
>Synopsis:       Creating lost+found causes fsck to stop fsck -y	FDIV017
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    nate
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  9 13:20:43 1995
>Closed-Date:    Sat Jun 29 15:59:45 MET DST 1996
>Last-Modified:  Sat Jun 29 16:01:36 MET DST 1996
>Originator:     Frank Durda IV
>Release:        FreeBSD 2.0.0-SNAP950322 i386
>Organization:
>Environment:

FreeBSD 2.0.0-SNAP950322 i386


>Description:

[FDIV017]

The first time FSCK runs after an installation and finds an unreferenced
file or directory, it creates lost+found.  This is OK.

However, fsck then reports:
	LINK COUNT INCREASING  (duh)
	UNEXPECTED INCONSISTENCY; RUN FSCK MANUALLY

	

>How-To-Repeat:

Cause a non-zero-length file or directory to be unreferences and run fsck
on a partition that doesn't have a lost+found.


>Fix:
	
I suggest that fsck should consider the inode (and associated links) it
used to create lost+found to not be an inconsistency. 
	

*END*

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->nate 
Responsible-Changed-By: scrappy 
Responsible-Changed-When: Sun May 26 13:45:07 PDT 1996 
Responsible-Changed-Why:  
did terry's patch include fix for this? 
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Sat Jun 29 15:59:45 MET DST 1996 
State-Changed-Why:  
Fixed after Terry's patch has been applied by Nate. 

>Unformatted:
 


