Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!necntc!dandelion!ulowell!page
From: page@swan.ulowell.edu (Bob Page)
Newsgroups: comp.sys.amiga
Subject: Re: A2000 Hard Drive Validation Problem
Message-ID: <8177@swan.ulowell.edu>
Date: 20 Jul 88 18:03:59 GMT
References: <640@oscvax.UUCP> <8132@swan.ulowell.edu> <4295@cbmvax.UUCP>
Reply-To: page@swan.ulowell.edu (Bob Page)
Organization: University of Lowell, Computer Science Dept.
Lines: 27

I wrote:
>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.

steveb@cbmvax.UUCP (Steve Beats) replied:
>Actually, the validator doesn't have the information.

Not at the time it detects the duplication, but it *did* have it, just
threw it away.

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

Great.  It only needs to go into this verbose mode if a bitmap
collision occurs... you'd just rescan the disk looking for references
to the block you know is referenced more than once.  Otherwise,
assuming every block might have multiple references would make you
construct a huge (depending on partition size) owner list for each
referenced block, clearly a waste of memory.

I think extended error messages in 1.4 will be perceived as just as
large an improvement in the file system as FFS is in 1.3.

..Bob
-- 
Bob Page, U of Lowell CS Dept.  page@swan.ulowell.edu  ulowell!page
"What a wonder is USENET; such wholesale production of conjecture from
such a trifling investment in fact."	-- Carl S. Gutekunst