Major dosFs2 problem with Hard Drive

[Ilan]

Hi,

In am working on 80Gb Hard drive ("big drive") and In my application I
have task that open files for writing ,write 30 Mb of data and close
the files and so on in while loop for more files.
after I run the chkdsk function I see that I have a lot error messages
as below for example:

"/AT3/mov493.dat" file larger then its chain of clusters Entry will be
deleted.
"/AT3 - lost chains " has illegal cluster in chain
"/AT3 - lost chains " cross-linked with another chain

I initialize my dosFs system in that way with the option
DOS_OPT_CHANGENOWARN:

if (pVolDesc=dosFsDevInit(bootDir, pBlkDev, NULL)) ==
(DOS_VOL_DESC *) NULL)
{
printErr ("Error during dosFsDevInit: %x\n", errno);
return (ERROR);
}

if(dosFsVolOptionsSetpVolDesc,DOS_OPT_CHANGENOWARN)==ERROR)
{
perror("dosFsVolOptionsSet");
}

I as well call the ioctl with the options FIOSYNC or FIOFLUSH after
every write
to take care of the synchronization (FAT32) but it doesn't help.
The HD is ATA/100 (Lba).

the printing of the function dosFsConfigShow() is:

current volume configuration:
- volume label: NO LABEL ; (in boot sector: )
- volume Id: 0x54414438
- total number of sectors: 156,301,488
- bytes per sector: 512
- # of sectors per cluster: 128
- # of reserved sectors: 32
- FAT entry size: FAT32
- # of sectors per FAT copy: 9,540
- # of FAT table copies: 2
- # of hidden sectors: 0
- first cluster is in sector # 19,112
- directory structure: VFAT
- root dir start cluster: 2

FAT handler information:
------------------------
- allocation group size: 123 clusters
- free space on volume: 76,867,371,046 bytes

I will be glad if someone have an idea how to solve this problem.
this is very important.

Thank you very much,
Ilan

[Leonid Rosenboim]

Ilan, I would recommend that you first make sure
that you are using a version of DosFs2.0 which has
all the lastest patches.

Also, you should search the archives of this newsgroup, e.g. on Google
Groups,
and you will find a couple of known problems and their solution.

My best guess is that you are using PPC604, and the problem you
experience is due to the compier improper handling of 64-bit integer
arithmetics, which is used extensively throughout dosFs2.0.
For that problem, there is a binary patch from WIndSurf or
a source work around (if you got dosFs2.0 source code).

Send my regards to both Davids and Daniel.
- Leonid

"Ilan" <il...@rugged.com> wrote in message
news:2d7af320.02021...@posting.google.com...