Date:	Mon, 15 Jun 1998 10:33:26 +1200 (NZST)
From:	Eric Gillespie <viking AT flying-brick DOT caverock DOT net DOT nz>
To:	Pavel Ozerski <pavel AT insect DOT ief DOT spb DOT su>
cc:	opendos AT delorie DOT com
Subject:	Re: The bug in CHKDSK?
In-Reply-To:	<AAZbeWrC11@insect.ief.spb.su>
Message-ID:	<Pine.LNX.3.96.980615102658.548A-100000@brick.flying-brick.caverock.net.nz>
MIME-Version:	1.0

On Sat, 13 Jun 1998, Pavel Ozerski wrote:

::Hello all,
::
::I found that CHKDSK in DR-DOS 7.02 seems to be buggy.
::I tried to repair errors on my HD using CHKDSK /F and got
::the strange message: "contains an invalid cluster.contains an invalid cluster.contains
::an invalid cluster... over and over again repeated - instead the prompt
::to save changes. Afterthem it corrected errors without prompt.
::A question to Caldera: is this bug (if it exists) a simple
::erratum or it is a result of the attempt to adapt this utility to long 
::file names (if this attempt was really?)?
I have noticed this effect under OpenDOS 7.01 with long filenames in the
root directory - what CHKDSK does (at least for 7.01) is read each
directory entry and try to follow the FAT chain for that entry - of course
if the entry is a LFN mathing one of the shorter names, it makes CHKDSK go
NATO and it goes looking for cluster number 445276622195 in the FAT or
something like that 8-) - it then can't find it, so it says () contains an
invalid cluster entry (but forgets to put a CR after the message) so if
you have more than one LFN in the directory, you get the strange effect
you mentioned.  I have abandoned the use of LFN for the moment (I'm having
too much fun with Linux now...) but would like to know if DR get this bug
fixed as I would like LFN working properly.

Anyway, that's all from me - let me know if this message gets through?  My
mailer has just been fixed, and this is the test message for the fixes 8-)

Bye
Cheeers from the Viking, Running Linux and Opendos in Christchurch.

- Raw text -