Path: utzoo!attcan!uunet!cbmvax!steveb
From: steveb@cbmvax.UUCP (Steve Beats)
Newsgroups: comp.sys.amiga
Subject: Re: A2000 Hard Drive Validation Problem
Message-ID: <4295@cbmvax.UUCP>
Date: 20 Jul 88 14:03:52 GMT
References: <640@oscvax.UUCP> <8132@swan.ulowell.edu>
Reply-To: steveb@cbmvax.UUCP (Steve Beats)
Organization: Commodore Technology, West Chester, PA
Lines: 27

In article <8132@swan.ulowell.edu> page@swan.ulowell.edu (Bob Page) writes:
>>KEY 24239 ALREADY SET.  Block 24239 happens to be a directory header block.
>
>[stuff deleted]
>
>It would also be nice if the validator helped you out here by telling
>you WHERE the duplicate references were, since it already has the
>information.  Maybe in KS 1.4.
>
>..Bob
>-- 
>Bob Page, U of Lowell CS Dept.  page@swan.ulowell.edu  ulowell!page

Actually, the validator doesn't have the information.  Validator works by
building a bitmap for a disk that doesn't have one because of a crash or
power was turned off before the bitmap was written.  Under the 1.2 filing
system, it's also possible to fill a disk with user data thus leaving no
room for the bitmap blocks on the disk so the bitmap has to be constructed
then too.  Validator maintains two bitmaps while it is running, one is a
visit map that tells validator which headers are referenced by other headers
and the other is the physical bitmap it is building.  Since there is only
one bit set in the visit map for each header referenced, there is no way
to tell which headers have the conflicting entries.

This is VERY likely to change for 1.4 (a little bird told me :-)

	Steve