Date: Sun, 9 Apr 1995 13:20:45 -0700 From: uhclem%nemesis@fw.ast.com To: freebsd-bugs Subject: bin/323: Creating lost+found causes fsck to stop fsck -y FDIV017 Message-ID: <199504092020.NAA01415@freefall.cdrom.com> In-Reply-To: Your message of Sun, 9 Apr 95 13:44 CDT <m0ry1yH-0004vsC@nemesis.lonestar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504092020.NAA01415>