--- In ib-support@y..., Helen Borrie <helebor@t...> wrote:

> At 11:12 AM 04-11-02 +0000, you wrote:
>
> >select count(*) from external_table
> >
> >raises an error
> >
> > COUNT
> >============
> >Statement failed, SQLCODE = -902
> >
> >I/O error for file "/tmp/external_table"
> >-Error while trying to open file
> >-Invalid argument
> >
> >Is this an known bug?
>
> Yes, it's a known problem with FirebirdSS-1.0.0.796-0.64IO on

some

> combinations of Linux kernel version and filesystem format.

The OS is

> being asked to address physical space that is past the end of

file. It's

> currently being resolved for a forthcoming 1.1 update release.

That may or

> may not solve your problem, though, since it might be that your

kernel

> version is too low to support 64-bit i/o. In the meantime,

use the 32-bit

> i/o version and hedge your bets on 2 Gb max file size.
>
> heLen

Hello Helen,

thanks for the fast answer.

I use the FirebirdSS-1.0.0.796-0.64IO with kernel 2.4.18 and ext3
filesystem. I have no other problems with files larger than 2 GB.
The firebird database itself is about 3 GB, so i have to use the
64-bit i/o version. The problem only occurs with external tables
larger than 2 GB.
Is the database access to the gdb-files also affected by this
bug? Can the system become instabil if i go on using the 64 bit
i/o version. It seems that concerning the gdb file, everything
works fine.

Thank again for your recommendation.

B.t.w. if i switch back to the 32 bit i/o firebird version, so i
have to backup/resotre the gdb file or can i use the same gdb
file with both versions?

Nils