At 11:52 AM 10/11/2003 +0100, you wrote:

>Yes, it is a distinct possibility. AFAIK, 4 Gb *is* the max file size on
>NTFS.
>
><<If you are getting "inconsistencies", I strongly recommend
>****stopping****
><<until you have tested out the upper limit. If you inherited that NTFS
><<partition from NT4 (it wasn't created by Win2K) then this is indeed your
><<problem. Provided you haven't corrupted the database, you will be able to
><<take a gbak of it, and restore it to multiple files.
>
><<heLen
>
>Thanks
>
>We've made some investigations:
>
>Max file size limit for NTFS is the size of disk partition.
>The computer in question has NTFS file system and the disks were formatted
>under win 2000.
>
>We will (to be on the safe side) set the database file size to 2Gb.
>
>But more than i think (and i think a lot ;-)) more i'm convinced that the
>problem is on Firebird side.
>If the problem arised from OS limits then the database would be corrupt, but
>it wasn't.
>
>Was Firebird tested for files above 4Gb ??

Of course! But it is absolutely filesystem specific. If your FS can take
partition-sized files then there would not be the problem I described.

For example, I have Win2K on a server here, but the NTFS partitions were
created under NT 4. I don't treat them as capable of read/write > 4 Gb
when I'm storing databases.

To get more insight into your problem, you would need to provide some
useful information about what seems to be going wrong...

heLen