Bug 323 - Creating lost+found causes fsck to stop fsck -y FDIV017
Summary: Creating lost+found causes fsck to stop fsck -y FDIV017
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: nate
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1995-04-09 13:20 UTC by uhclem%nemesis
Modified: 1996-06-29 15:01 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description uhclem%nemesis 1995-04-09 13:20:43 UTC 
[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

Fix: 

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

*END*
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.
Comment 1 scrappy freebsd_committer freebsd_triage 1996-05-26 21:45:07 UTC 
Responsible Changed
From-To: freebsd-bugs->nate

did terry's patch include fix for this?
Comment 2 Joerg Wunsch freebsd_committer freebsd_triage 1996-06-29 14:59:45 UTC 
State Changed
From-To: open->closed

Fixed after Terry's patch has been applied by Nate.