From owner-freebsd-bugs  Sun Apr  9 13:20:49 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA01425
          for bugs-outgoing; Sun, 9 Apr 1995 13:20:49 -0700
Received: (from gnats@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA01415
          ; Sun, 9 Apr 1995 13:20:45 -0700
Date: Sun, 9 Apr 1995 13:20:45 -0700
Message-Id: <199504092020.NAA01415@freefall.cdrom.com>
From: uhclem%nemesis@fw.ast.com
Reply-To: uhclem%nemesis@fw.ast.com
To: freebsd-bugs
Subject: bin/323: Creating lost+found causes fsck to stop fsck -y	FDIV017
In-Reply-To: Your message of Sun, 9 Apr 95 13:44 CDT
	<m0ry1yH-0004vsC@nemesis.lonestar.org>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         323
>Category:       bin
>Synopsis:       Creating lost+found causes fsck to stop fsck -y	FDIV017
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  9 13:20:43 1995
>Originator:     Frank Durda IV
>Organization:
>Release:        FreeBSD 2.0.0-SNAP950322 i386
>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*

>Audit-Trail:
>Unformatted: